On Mon, Jan 19, 2004 at 07:14:19AM -0600, Chris Josephes wrote:
>
> I think sooner or later, we're all going to have to bite the bullet and go
> with Java class naming conventions, like
>
> org::simon-cozens::MVC
>
> or maybe Larry's recommendation of using CPAN id as a top level.
>
> simon::MVC (or maybe au::simon::MVC)
>
> Otherwise, CPAN will continue to grow wide at the top level.
I would rather CPAN be wide at the top level than have un-intuitive
names. The author based system will also become more difficult when
authors change hands, disappear, or there are multiple authors.
I tend to look for new modules by keyword search anyway. I don't
feel like I can depend on looking in any top-level name space and expect
to find all the modules that belong there.
Also, as long as names are sufficiently descriptive, I would just assume
they be shorter, rather than having fewer top-level name-spaces with
longer names.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
