Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

Oooh... More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Protect thy namespace! (Score:3, Insightful)

by johanvdb (1872) <johan (at) vandenbrande (dot) com> on 2003.04.17 8:13 (#19234) Journal

I wonder ... can't we lock some name spaces on CPAN, so that not everybody can update reserved module names?

I know it is a bit against the free-for-all culture that has been been the driving factor behind CPAN. but, be real, we should take care to make the pollution of CPAN less obvious ;-)

I'm not talking about rigorous measures here, we need to make sure CPAN stays open and free for non critical namespaces. But we should also have a more restricted access policy to some Perl core name spaces. Maybe modelled after the way a registered name space is granted for the moment - by using the mailing list ...

Just my 5€ cents ...

Johan

Reply to This

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.