Hi, Paul!
The debugger skipping over specific classes sounds really great. However, at
the risk of sounding greedy, it seems I can envision scenarios where I would
like to skip over methods in a class (like the String constructor) without
skipping the whole class. I admit it is rare, and you should not worry about
it if it slows down design of this functionality significantly. But if it is
easy to work it in from the start, I think it might be useful.
Marc-Antoine
-----Original Message-----
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 28, 2000 5:31 PM
To: Sergey A Klibanov; [EMAIL PROTECTED]
Subject: Re: Stepping into a constructor in JDEbug
At 04:14 PM 7/28/00 -0500, Sergey A Klibanov wrote:
>How do I step into a constructor of one of my own classes? Whenever I step
>into a new SomeClass() statement, it goes into the java class loader code.
>I would expect it to take me to the first line of the constructor of that
>class. The work-around is to open up SomeClass.java in another buffer and
>set a breakpoint at its first line, however this is tedious.
>Given that the class loader code is actually what gets called, I think it
>would be good to skip past that. Also, skipping over the String
>constructor in a statement like System.out.println("foo") would probably
>also be a good idea.
I plan to add the capability in a future release to allow you to specify
classes to skip, including the class loader, when stepping through an
application.
- Paul
