On Sun, Oct 28, 2001 at 12:58:45PM -0800, Terrence Brannon wrote: > I know of no other package which attempts to reserve a top-level > namespace for itself. In fact, CPAN strongly advises aginst this > practice.
I think you're refering to creating new top-level modules names (ones with no colons in them). You're also probably refering to a document I wrote (since I was the author of the Module List). You'll also find my contributions appearing frequently in the early days of the Modules mailing list where much of the current 'accepted standards' and 'case law' of module naming was thrashed out over many years. http://www.xray.mpe.mpg.de/cgi-bin/w3glimpse/modules?query=Tim+Bunce&errors=0&maxfiles=1000&maxlines=3000 > Compare with CGI, another module of equally wide use. I am > aware of no attempt my Lincoln Stein to reserve CGI::* for modules > developed for specific use with CGI.pm. CGI stands for Common Gateway Interface, an official standard not defined by Lincoln. No matter what Lincoln does with CGI.pm or others do with CGI::* modules, the Common Gateway Interface standard remains the same. The DBI is it's own standard and that standard is defined, to a certain extent, by the contents of the DBI:: namespace. The DBIx::* namespace exists to provide a natural (and florishing) home for modules that are closely tied to the DBI but not actually part of it. Bottom line: It's reserved because I'd like it to be reserved, and that's because I think it's in the best interests of the Perl community. Tim.
