develooper Front page | perl.perl5.porters | Postings from June 2011

Re: Can we do global bug fixes that change behavior?

Thread Previous
Jesse Vincent
June 29, 2011 06:10
Re: Can we do global bug fixes that change behavior?
Message ID:

On Tue, Jun 28, 2011 at 11:58:01PM +0200, Christian Walde wrote:
> On Tue, 28 Jun 2011 23:45:07 +0200, Jesse Vincent <> wrote:
> >On Tue, Jun 28, 2011 at 11:31:57PM +0200, Christian Walde wrote:
> >>xdg suggested on IRC that i ask this as a separate question, so:
> >>
> >>obra:
> >>
> >>Assuming p5p reaches an agreement that magical newline-changing on Windows is a bug, would you agree to changing the behavior globally for the interpreter; or only accept it as a lexical fix when 'use v5.16' is in effect no matter what the concensus is?
> >
> >I would strongly prefer the latter.
> Maybe i should've added this too: The question is asked because an outright and absolute refusal of the former means that i'd need to stop spending time here and look into other, less wholesome, venues; since a lexical-only fix for this is flat out use- and pointless.

My gut feeling is that such a change to the no-declared-version default
would cause a lot of code in the wild to break. I don't like us hurting
our users.

I've come around to believing that we need to move toward making
use v5.16+ not just a low-tide mark but a description of what version of 
Perl's semantics you expect.

That's the bulk of my YAPC/OSCON/YAPC::EU talk this year. I'm preparing
a variant that will make sense as text that I can post to p5p.


Thread Previous Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About