On Mon, 10 Feb 2003, Steve Linberg wrote: > Yes, that's what I was referring to earlier, but it's not quite the > same thing. I could "bury" things in Local::, but I guess part of > the issue is that these are modules I might like to actually release > someday, if I ever feel they're good enough and might be useful to > others, and I'd like to be able to do that without changing > Local::Foo references everywhere I've referenced them.
This might be a Good Thing [tm], as it would make sure you don't accidentally rely on any other Local:: modules in a public release. > I could see the top-level namespace becoming very polluted with > Foo_Corp::* references, so I was wondering if there was any top-level > namespace that could be used for grouping modules from particular > sources (i.e. a small company's miscellaneous utilities). I could > just use "SGT::*" hoping that my choice of acronym "SGT" remains > unused at the top level, but if there were one level above that that > was for all such groupings, the chance for collision would be greatly > reduced. > > In other words, something like Corp::SGT::*, so you have any number > of second-tier "Corp" groupings, but only the one Corp:: top-level > namespace entry. I could see that working. > I know this isn't a huge problem right now and there's plenty of > room, but I always like to try to start off on the best possible > footing so drastic change is less likely to be needed later. > > Would a top-level Corp:: (or something else?) be a useful thing to > suggest to the CPAN maintainer? Or is this just out in space and not > needed? My concern would be that it would break the general style of having the namespaces refer to the function of the module not it's author. Even with search.cpan.org it would be very easy for good modules to be "lost" in the maze of Corp:: modules. I think on the whole I like the Local:: then port to a main namespace idea over the Corp:: idea. That said, there is some argument perhaps for a Corp:: namespace for code that is not being publicly released, but is more widely distributed, e.g. to a client site but even then a Foo_Corp:: namespace would serve just as well here. > Trying to be a good Perl/CPAN citizen, Aren't we all :) Simon. _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
