On Wed, 19 Jul 2000, Nathan Meyers wrote:
> On Wed, Jul 19, 2000 at 03:54:40PM +0000, Kris Heyrman wrote:
> > Hi,
> >
> > I think I am getting stupid: I just spent a day trying to find out how best to
> > debug a project that is getting fairly complicated, in Java. I did not find out
> > how, so I am asking the question. Hopefully, somebody can give me a hint.
>
> I've had some success using the Inprise JBuilder product (personal
> edition is free), although I still do most of my debugging with print
> statements. A surprising number of other developers I've talked to,
> working on various platforms, say the same thing. Bottom line: the
> state of debugging technology is depressing.
>
Nathan,
it's depressing that println is the most common debugging tool. I don't
use a debugger religiously but even jdb (with Emacs bindings) is preferred
over sprinkling printlns (which sadly do sneak into production
code). VisualAge for Java has a pretty slick debugger, but their
development environment is very pervasive (or invasive if you will).
On the plus side, many developers seem to religiously run test cases
nowadays, which does aid in isolating problems.
:ml
--JAA32418.964197274/c806001-b.pinol1.sfba.home.com--
ReSent-Date: Fri, 21 Jul 2000 09:53:42 -0700 (PDT)
ReSent-From: Man Chi Ly <[EMAIL PROTECTED]>
ReSent-To: [EMAIL PROTECTED]
ReSent-Subject: Re: Debugging Java on Linux with JDK1.2.2
ReSent-Message-ID: <[EMAIL PROTECTED]>
On Wed, 19 Jul 2000, Nathan Meyers wrote:
> On Wed, Jul 19, 2000 at 03:54:40PM +0000, Kris Heyrman wrote:
> > Hi,
> >
> > I think I am getting stupid: I just spent a day trying to find out how best to
> > debug a project that is getting fairly complicated, in Java. I did not find out
> > how, so I am asking the question. Hopefully, somebody can give me a hint.
>
> I've had some success using the Inprise JBuilder product (personal
> edition is free), although I still do most of my debugging with print
> statements. A surprising number of other developers I've talked to,
> working on various platforms, say the same thing. Bottom line: the
> state of debugging technology is depressing.
>
Nathan,
it's depressing that println is the most common debugging tool. I don't
use a debugger religiously but even jdb (with Emacs bindings) is preferred
over sprinkling printlns (which sadly do sneak into production
code). VisualAge for Java has a pretty slick debugger, but their
development environment is very pervasive (or invasive if you will).
On the plus side, many developers seem to religiously run test cases
nowadays, which does aid in isolating problems.
:ml
--JAA32418.964197274/c806001-b.pinol1.sfba.home.com--
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
