Front page | perl.perl5.porters |
Postings from February 2009
> If the warning is "we don't recommend using this in new code, FOO::BAR > has a better interface" then there's nothing hypocritical about using it > in old code. It'd be a fairly radical change for p5p to start pushing an agenda about which Perl modules shouldn't be used in new code. Getting modules out of the core is a different discussion from telling users of those modules that their existing code needs to change. One of the great things about Nicholas' @INC hacking and dual-lifed modules is that they can live out the rest of their existence without cluttering the core. If we're making "official" judgement calls about which modules should stop being used for new code, then um.. Perl is infested with bad code. I have here in my hand a list of 50 -- A list of modules in the core and on the CPAN which are known to be bad code and which nevertheless are still being used and still shaping Perl programs today. -jThread Previous | Thread Next