Re: Carrots and Sticks
> Perhaps there needs to be something like an $API package variable
> which changes when the module API changes significantly?
I use a named argument in the constructor:
my $foo = Foo::Bar->new ('-api' => 'xeen');
> [1] ick, ick
I'm not sure whether it's a waste of code/cpu or not, so I don't use
that approach with all my modules. Luckily, I don't think anyone
else uses my modules.
-Hao
Re: Carrots and Sticks
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 significantly?[1] 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? Leon [1] ick, ick -- Leon Brocard.http://www.astray.com/ yapc::Europe - September 22-24 London - http://yapc.org/Europe/
