Hi Staffan, thanks for your feedback.
The fingerprint algorithm may be either:
- added to javac as an argument, in order to calculate during
compilation and inject that to the classfile format "new attribute"
- a new tool provided by JDK, say "javafp" that would be allowed for
standalone calls
Hi Bruno,
This is an interesting proposal and I guess it would avoid a lot of unnecessary
confusion for developers.
As I understand it, the exact algorithm used to compute the fingerprint would
need to be known to debuggers, or at least an implementation of it would need
to be provided by the
Hi all,
Based on a common incident that happens not rarely among developers, and
as recently felt by Martijn Dashort [1], it seems to be a good idea to:
"Enable debugger to detect when there is a mismatch between source code
and class being debugged" (thanks to Stuart Marks for the excellent
