There is a step-over function. The problem arises when a single line
incorporates calls to both system and application methods, and you do
want to step into the latter. The design that I have heard mentioned
would make it configurable whether or not you want to be able to step
into system methods.
Chuck Irvine
-----Original Message-----
From: mass [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 09, 2000 3:42 PM
Cc: mass; jde
Subject: RE: avoid stepping in "system" functions
isn't there a 'step over' function? I personally like being able to go
into system libraries if needed.
-David Waite
On Wed, 9 Feb 2000, Tibor Janosi wrote:
>
>
> This is exactly what I was thinking about myself. Having a simple
> configuration file that just lists the packages that should not be
stepped
> in would be great. The user could add/remove packages (and maybe even
> classes within packages) to simplify and speed up debugging.
>
> Maybe a variable in a project is not the best way to go since there
are
> many classes that you ordinarily don't want to debug.
>
> Tibor
>
> > >The idea, I think, is to automatically step out of all classes in
certain
> > >packages, e.g., all classes in java.lang.
> > >
> > >This is, I take it, not easy to do?... To define, e.g., a variable,
as part
> > >of a
> > >project, that defines packages / paths out of which to step, as
soon as they
> > >are
> > >stepped into?...
> > >
> >
> > Perhaps it is. I will try implementing this.
>
>
>
