Re: [Objectbridge-jdo-dev] ojb suitable for jdo implementation

[Sebastian K. <seb...@mu...>]

On Sunday 12 May 2002 16:00, Christian Sell wrote:
> > - Enhancement is another step in the build process and can make debugging
> > difficult
>
> slightly off-topic, but this is one of the statements that one always gets
> to hear when the disadvantages of enhancement are discussed. Yet I do not
> understand why this should be so. The Java Bytecode and debugger interface
> are all well documented, so it should be rather trivial to make the
> enhanced bytecode completely transparent with regard to debugging.

well, of course, the enhancer has to take care, that line-information isn't 
lost, but I guess, that some debuggers have problems when the command to be 
executed is a method call (for example to jdoGetXXX), but the source code is 
a "localVariable = this.persistentMemberVariable". If you now give the normal 
"step" command the debugger will step into a method where he does not expect 
one and that does not exist in the source code. Perhaps "simple debuggers", 
that only rely on the line-numbers work better here, that debuggers that 
analyze the source-code.

However, the jdo spec seems to make pretty clear, that debugging should not 
be a big problem, I only wanted to mention it.

ciao Sebastian

-- 
Sebastian Kanthak    |    seb...@mu...