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

Re: Shouldn't "Unrecognized escape foo..." messages be changed to deprecated class?

Thread Previous
From:
demerphq
Date:
May 19, 2010 07:22
Subject:
Re: Shouldn't "Unrecognized escape foo..." messages be changed to deprecated class?
Message ID:
AANLkTika25IDDgF2fRD04flJX0UlQaIABuTUvrD_Can7@mail.gmail.com
On 19 May 2010 16:12, Jesse Vincent <jesse@fsck.com> wrote:
>
>
>
> On Wed, May 19, 2010 at 06:59:34AM -0600, karl williamson wrote:
>> Now that we have deprecated messages that are by default on, it
>> seems to me that these ones should be changed to have that behavior.
>>
>> We fee free to take over foo at any major release, so they are
>> effectively deprecated.
>
> Except they're not deprecated. Your description sounds more like
> "reserved" than deprecated.

Right. Basically they are "use at your own risk".

If quotemeta() doesn't escape it, then it shouldn't be escaped.

cheers,
Yves


-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

Thread Previous


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