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

Re: How on earth did we manage to break pack() so badly?

Thread Previous | Thread Next
From:
demerphq
Date:
May 7, 2013 06:59
Subject:
Re: How on earth did we manage to break pack() so badly?
Message ID:
CANgJU+WNUS7o7=4P6dfo7G42jXkBjKv73ufeNaZH0jQutZYHUQ@mail.gmail.com
On Tuesday, 7 May 2013, Steffen Mueller wrote:

> On 05/07/2013 12:21 AM, Ricardo Signes wrote:
>
>> * demerphq <demerphq@gmail.com> [2013-05-01T10:32:07]
>>
>>> [pack is a mess]
>>>
>>
>> I would like to address "the pack problem," but am going to avoid wading
>> into
>> this until 5.18.0 is shipped, as my time has been crunched lately.  So
>> I'm just
>> writing to say, "I care and will write more," that that's all.
>>
>
> That's likely the best choice in the circumstances and I would probably do
> the same in your shoes. Not a 5.16=>5.18 regression and we can't let 5.18
> wait for all bugs forever.


for sure. i never meant that we should fix for 518.


> Nonetheless, if we're going to upgrade to 5.18 at work, I could entirely
> see this as being the first case of us not using a pristine upstream perl.
> We've been actively trying not to go down that path.
>
lets hope we dont have to do this

yves on ipad


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

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