🚀 go-pugleaf

JD:

JB has to find a runnable node in a piece of source code.  We look for
main() or init() as a top level node and use the first one we find as
the "runnable node".

You really wouldn't want us to have to parse, entirely, all files in a
project just to find a hidden main()!  Well, the other 99% of the
world wouldn't like the wait <g>.

That particuler tip from Bruce still doesn't strike me as beneficial
(and he didn't originate it, either) beyond being a piece of "ego
code"  ("Hey, look what *I* can do!"), but if it has some real world
gain for you, great!

-Rich

JD wrote:
> 
> I'm having trouble debugging a main() inside an inner class.  Here's the
> code:
> 
> public class TestInner{
>     public TestInner() { }
> 
>     static public class Inner{
>         public static void main(String args[]){
>             System.out.println("some output");
>         }
>     }
> }
> 
> It compiles fine, and runs from the command line (java TestInner$Inner)
> but I can't run/debug it from JBuilder.  I get a message: "Cannot
> determine runnable file".  I can't set TestInner$Inner to be the default
> runnable, even if I edit the jpr file by hand.  This works in J++.  Any
> ideas?
> 
> P.S. If you're wondering why the hell I'd do this, check out Bruce
> Eckel's excellent book _Thinking_in_Java_.

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=