syphilis has asked for the wisdom of the Perl Monks concerning the following question:
Now, I know the commit was not made in time for 5.18.0 (because I have 5.18.0, and it displays the old behaviour) ... and I know it *is* in 5.20.0 (because I have 5.20.0 and it displays the new behaviour).commit b127e37e51c21b0a36755dcd19811be931a03d83 Author: Karl Williamson <pub...@khwilliamson.com> Date: Mon May 13 07:35:35 2013 -0600 PATCH: [perl #108378] [perl #115800] This patch solves two tickets. Both are a result of the stringification of a floating number being sticky, so that the character representing + the decimal point may be from an old locale. The patch solves this b +y not retaining the stringification of NVs.
On 5.18.0, the Dump() reveals that the set flags are (NOK,POK,pNOK,pPOK)C:\>perl -MDevel::Peek -le "$x = 2.7; print $x; Dump $x;"
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Determining if a change in perl was backported
by dave_the_m (Monsignor) on Nov 07, 2016 at 13:15 UTC | |
by choroba (Cardinal) on Nov 07, 2016 at 17:09 UTC | |
|
Re: Determining if a change in perl was backported
by Tux (Canon) on Nov 07, 2016 at 17:06 UTC | |
|
Re: Determining if a change in perl was backported
by beech (Parson) on Nov 07, 2016 at 19:50 UTC | |
|
Re: Determining if a change in perl was backported
by syphilis (Archbishop) on Nov 08, 2016 at 10:41 UTC |