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=-
Tim Bray wrote:
>
> Hi - I've been building some big complicated chunks of J3D code by brute
> force, just compiling and running and debugging with System.err.println,
> all in a DOS window. Not bad, but not ideal either.
>
> So.... which of the visual dev environments are people using successfully
> with J3D? -Tim
>
> ===========================================================================
> 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".
===========================================================================
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".
