On Sun, May 26, 2013 at 04:23:46PM -0700, rh <[email protected]>
wrote:
> I haven't been paying attention to perl for a while now and this
> is the first I heard of 5.18 release. Sad to hear it's this broken.
The problem is that the group "perl5porters" has changed considerably -
cpan compatibility isn't as important as having new exciting experimental
perl6y flashy stuff that is so broken it has to be redacted a few releases
later. In fact, the current perl5 pumpkin is the former perl6 maintainer,
with exciting new ideas on how to fix and imrpove the ugly perl language.
As such, p5p doesn't even consider 5.18 broken. It's perl itself and cpan
that is broken, and 5.18 is merely part of the fix.
> I thought perl-porters were pretty diligent about testing.
That was absolutely true in the old days (not so long ago). Now breaking
CPAN modules is considered "not our problem" (quote by Yves who made the
patch that broke DBI, LWP and a hundred others).
There are still a few who do care, of course.
> Are they intending to leave these? Is it up to the module maintainer to
> fix the module or is 5.18.1 coming soon?
It's up to the module maintainers to fix the 5.18 breakage (apart from a
few people who still care and try to send patches, but even then, it's up
to the module maintainers). Modules that don't catch up quickly enough
are simply left behind, compatibility to older perl versions or older
documented features is not important.
This is, of course, my biased view - stability is of major importance to
me, having invested a lot into perl. Sadly, this is no longer true for
p5p.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
