develooper Front page | perl.perl5.porters | Postings from August 2010

Re: qr stringification: why are xism always present? I'm worriedabout backward compatibility

Thread Previous | Thread Next
From:
Eric Brine
Date:
August 20, 2010 07:19
Subject:
Re: qr stringification: why are xism always present? I'm worriedabout backward compatibility
Message ID:
AANLkTi=X7dCVfhwM+7sPpt_Fr9+yB2miDcP3z-27=tWS@mail.gmail.com
On Fri, Aug 20, 2010 at 8:40 AM, Aristotle Pagaltzis <pagaltzis@gmx.de>wrote:

> [Note: the following reply is based on the consensus reached in
> previous discussion.]
>
> * Abigail <abigail@abigail.be> [2010-08-19 16:40]:
> > After reading the entire thread, I can't say I really see the
> > benefits of the proposed (?~) construct. Sure, with enough
> > imagination, one can think of obscure contructs that will
> > break. OTOH, in the past, I've written code that actually scans
> > for (?xism:) constructs and modifies them. Such code would
> > break if (?xism:) is going to be replaced with (?~:).
>
> Such code will break anyway, because the default will soon change
> to include a new flag that specifies the Unicode behaviour.
>

Furthermore, switching to (?~:) will avoid breaking code when we add /z to
5.18 (for example). (?~:) breaks less.

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About