On Friday 05 April 2002 02:43 pm, Leo Simons wrote:
> 6): java does not allow duplication in descriptive names among peers.
> 7): we want our projects to be flat, ie using a structure like
> org.apache.${projectname}.${packagename}.
> 8): 6) + 7) -> purely descriptive names are not always an option. We will
> use nondescriptive names instead in those cases.
(my ad&d and king arthur knowledge is shabby at best).
IMHO, descriptive names are best for classes. In case 8, how about a
comprimise such as the ExcaliburComponentManager. Its a unique name but
identifies a component manager from Excalibur. In the same token you could
have a DaggerComponentManager, BroadswordComponentManager, etc, etc. But just
having a class called Dagger, doesn't do me much good unless you stare at it
all day.
For those of us that are more users of Avalon rather than users + developers,
I find that I don't have to deal with the "internal"-ish classes very much
component mgr + friends. I have that infrastructure set up and thanks to the
beauty and elegance of the framework I just spend my time with the lifestyle
interfaces and my components. It is very nice to have descriptive class and
interface names when I do go back to look at the underlying avalon code,
though.
Anyways that's kind of rambly, but please don't name classes/interfaces
solely after non-related things. At least prefix.
-pete
--
peter royal -> [EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
