#2 Line #s of line in original source

[Bill Bumgarner]

It would be really handy to have the line # of the
decompiled bit of source as it was in the original
file.

I.e. if jode produces:

public PeerGroupID getPeerGroupID() {
PeerGroupID peergroupid = new
PeerGroupID(new UUID(0L, 0L));
return peergroupid;
}

I would like to see:

public PeerGroupID getPeerGroupID() {
/* 280 */ PeerGroupID peergroupid = new
PeerGroupID(new UUID(0L, 0L));
/* 282 */ return peergroupid;
}

This will make the jode output 10x more useful
when using jode to analyze exception
backtraces....

[Jochen Hoenicke]

Logged In: YES
user_id=18252

I will do it, but I can't promise how quickly I get to it.
It needs a bit of coding to propagate the line number
information from the bytecode opcodes to the java
expressions.

[Cay Horstmann]

Logged In: YES
user_id=725563

I'd like to second this request. I used JODE to reverse
engineer the code from the Java Server Faces reference
implementation. It has been a lifesaver.

However, the servlet container throws exceptions all the
time, at the slightest provocation. Having to use javap in
conjunction with the JODE disassembly is a pain.

[Aaron Optimizer Digulla]

Logged In: YES
user_id=606

Please put the line number at the end! This wouldn't disrupt
the formatting.

Adding a # in front of the line number would make it easy to
search for it.

Even more interesting would be to reorder the source when
you find line numbers (adding empty lines when
necessary).For a simple and good result, first sort the
methods by line number and then check if each of them "fits"
into it's space (number of lines upto next method). If it
doesn't, move this method after the last one (so the least
amount of methods is moved).