🚀 go-pugleaf

Greg Hamer <ghamer@inprise.com> wrote:
> The java stuff and jbcl are not delivered with debug info. You can
> re-compile them yourself  with the debug flag turned on. I am amazed that
> more people do not scream about this.

What I have done when I run into this problem is to browse to the source
for the class that I need debug info on, then press the compile button. 
This creates .class files in my class output directory containing the
needed debug information, which allows me to examine variables when I trace
into it.

I have not tried rebuilding an entire class library, since the entire
source is not always included.  Has anyone actually tried doing this?  Are
there any pitfalls?

What really surprises me is that Borland does not distribute libraries
compiled with the debug flag.  The ability to trace into library classes
(and be able to see something useful, as opposed to what you get with what
Borland provides), is an essential part of a Java development environment.

-- 
John P. McGrath
<mcgrath@enter.net>
<jpm@nscs.fast.net>