Front page | perl.perl5.porters |
Postings from August 2010
On 26 August 2010 12:36, Abigail <abigail@abigail.be> wrote:
> On Thu, Aug 26, 2010 at 12:15:48PM +0200, demerphq wrote:
>>
>> Lastly, im inclined to say that we should raise the priority of this
>> ticket, I think it is somewhat serious. At the very least we should
>> make sure that this "optimisation" is disabled As Soon As Possible in
>> 5.12 - its one thing to be slow, but being *wrong* is really bad.
>>
>> Im actually inclined to say that this might be important enough to
>> delay the next 5.12.x release until it is fixed. (I think disabling it
>> should be relatively quick to do, i just dont have enough contiguous
>> time in my schedule to *promise* it myself - I will try, but....)
>
>
> Considering this bug has been present since at least 5.8.5 (but not in
> 5.6.2), is it really that important to delay the next 5.12 release? I'd
> think the world can survive one more release with this bug.
Well, true, however given how much people rely on the regex engine and
how easy this particular bug is to fall into im a little worried.
I guess we could just add a note in perldelta saying "known bugs" and
including a workaround (use the {1} modifier).
> Enjoy the rest of your vacation.
Thanks, unfortunately the weather has not been particularly kind to us
this year....
Cheers,
yves
--
perl -Mre=debug -e "/just|another|perl|hacker/"
Thread Previous
|
Thread Next