Garrett Goebel sent the following bits through the ether:

> I guess the next question for Perl6, is where does conventional wisdom leave
> off and rapid ankle biting conformancy and normalization of peoples' code
> begin? I.e. where is the carrot and the stick?

Well why *aren't* people following perlstyle? ;-p

I don't think people will be happy with a CPAN naming convention
police, but otoh I don't see modules changing completely if they then
get inserted into the core. Perhaps there needs to be something like
an $API package variable which changes when the module API changes

At the moment I guess this is being done by renaming modules (ie
Foo::Bar becoming Foo::Bar2). I remember Larry saying something about
making it easier for multiple versions of modules to coexist
properly. Would that solve this problem?


[1] ick, ick
Leon Brocard.............................
yapc::Europe - September 22-24 London -

Reply via email to