NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Straw man (Score:2)
I don't think chromatic is proposing that Perl start break back compat willy nilly. He's been quite clear that he wants to see Perl on a time-based release cycle with published deprecation schedules.
Imagine if Perl release 4 times a year. Then if there was a desire to deprecate something, a release could say "feature X will be removed after 6 more releases, 18 months from now".
That seems pretty reasonable.
Furthermore, no one out there is jumping from 5.6 to 5.10 without some serious testing. Even with Perl'
Silly autarch! Urth is for adults! (Score:1)
Is "because fuck you a year from now" that much better than "because fuck you?" I like the way my Perl programs keep working when I copy them to a machine where the sysadmin has decided to install the "latest and greatest." The sysadmin likes the way I don't ask him to install an old Perl to un-break my working programs.
Re: (Score:2)
So you expect the Perl core folks instead to do all the work for you, and ensure that when you do something that's likely to be unsafe, it's safe anyway.
That's ridiculous.
Re:Silly autarch! Urth is for adults! (Score:1)
You missed "for free", "for longer than a decade", and "without seeing your code or even knowing that it exists."
Reply to This
Parent