Article View: borland.public.jbuilder.java.language
Article #14702Q: Why does the app generator use Inner Classes?
From: Edward Wildgoose
Date: Mon, 16 Aug 1999 00:00
Date: Mon, 16 Aug 1999 00:00
24 lines
1463 bytes
1463 bytes
Bit of a newbie question, but:
Creating a new project of type "Application" walks me through a series of
dialogs and then generates a Frame class, an AboutBox class and a main
application class, etc. I am trying to get my head around the basic
framework that I should use for my own applications and one of the things I
am puzzled by is why the app generator appears to create each of these
classes as an inner class with the same name as the outer class...?
eg Class MyFrame{
Class MyFrame { /*Class definition here*/ }
}
I am aware of inner classes from a syntactic point of view, but I can't
understand why this is a useful construct in this case? When is it useful
to copy this method? What are the pros and cons as opposed to a straight
class with Access control modifiers?
One of the cons appears to be that my UML tool can't really understand what
is going on!
Thanks
Ed Wildgoose
Technical Details
Message-ID:
<7p8s6h$ooh7@forums.borland.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f74b3,a3d0dac787052894,start X-Google-Attributes: gidf74b3,public From: "Edward Wildgoose" <Ed@ewildgoose.demon.co.uk> Subject: Q: Why does the app generator use Inner Classes? Date: 1999/08/16 Message-ID: <7p8s6h$ooh7@forums.borland.com> X-Deja-AN: 513334824 X-Priority: 3 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Organization: Another Netscape Collabra Server User X-MSMail-Priority: Normal Newsgroups: borland.public.jbuilder.java.language