JBuilder v3's debugger uses the Sun JDK with the new debugger hooks, so
this is not a problem. Seems to work great with Java3D.
However, I have stopped using JBuilder because
there is minor bug in 3.0 that makes it unusable for me. When an
application is run or debugged under JBuilder, the initial directory of
the process is random within the classpath (as opposed to always starting
at the location of the project file, as happened in JBuilder 2). So if
you intend to read in configuration files relative to the local directory,
the system is useless.
I have occationally opened up JBuild to do thread debugging because it's
does have nice thread debugger. But I have gotten the impression from
this limited usage, that JBuilder 3 is actually less stable than the
lastest release of JBuilder 2.
On Tue, 7 Sep 1999, Vladimir Olenin wrote:
> System.out.println is the best and forever :) . Actually JBuilder has
> not a bad debugger. Or to be more correct, _HAD_, since i don't use it
> anymore (for about half of a year). The problem was that the time i left
> it they used their own version of JDK for debugging. So, first Sun
> release SDK, then Inprise team rebuild it, them they release there next
> version of Builder. I recall tough argueing between Inpise and some
> developers right about debugging for JDK2 (still beta version that
> time). Possibly in JBuilder3 everything has changed for good. Moreover
> as i heard Sun too continueosly extends debugging features of their VM.
> So, one day we'll get all this. I hope.
>
> So far i prefer to use good old println (BTW, it looks like Sun guys use
> it either: just have a look at their util classes)
>
> -=V=-
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
