Branch: refs/heads/psc/ppc0025
  Home:   https://github.com/Perl/perl5
  Commit: 9eacc8fb7c86c252d789b58c3b2e76074ec80e51
      
https://github.com/Perl/perl5/commit/9eacc8fb7c86c252d789b58c3b2e76074ec80e51
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M Configure
    M Porting/makerel
    M myconfig.SH
    M perl.c
    M perl.h

  Log Message:
  -----------
  drop the 5

This commit drop PERL_REVISION from $] and $^V.

Since $^V expects 3 components, we add a .0 at the end.


  Commit: de60ecdc84a72e3ccb72054e132babf5ec31b2d8
      
https://github.com/Perl/perl5/commit/de60ecdc84a72e3ccb72054e132babf5ec31b2d8
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M lib/feature.pm
    M regen/feature.pl

  Log Message:
  -----------
  create the :42 feature bundle

The FEATURE_BUNDLE_xxx constants in feature.h must be ordered by
version. The 'as_bundles' sort function ensures that all bundles will
be sorted correctly (except for 5.9.5, which ends up between 5.41 and 41).


  Commit: f7c41d85a067d74d67d095d912f31d9f05316fb7
      
https://github.com/Perl/perl5/commit/f7c41d85a067d74d67d095d912f31d9f05316fb7
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M t/run/switches.t

  Log Message:
  -----------
  fix the test for perl -v


  Commit: 376914456c10bc11acc61d438b88cfe10f8d618a
      
https://github.com/Perl/perl5/commit/376914456c10bc11acc61d438b88cfe10f8d618a
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M cpan/CPAN-Meta-Requirements/t/from-hash.t

  Log Message:
  -----------
  [CPAN-Meta-Requirements] fix string comparisons with $] to use numeric 
comparison instead

The fix follows Zefram's suggestion from
https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186846.html

> On older perls, however, $] had a numeric value that was built up using
> floating-point arithmetic, such as 5+0.006+0.000002.  This would not
> necessarily match the conversion of the complete value from string form
> [perl #72210].  You can work around that by explicitly stringifying
> $] (which produces a correct string) and having *that* numify (to a
> correctly-converted floating point value) for comparison.  I cultivate
> the habit of always stringifying $] to work around this, regardless of
> the threshold where the bug was fixed.  So I'd write
>
>     use if "$]" >= 5.014, warnings => "non_unicode";


  Commit: e570b86e230be8b291449a1198b8a83ed16dcf45
      
https://github.com/Perl/perl5/commit/e570b86e230be8b291449a1198b8a83ed16dcf45
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M cpan/CPAN-Meta/lib/CPAN/Meta.pm

  Log Message:
  -----------
  [CPAN-Meta] fix string comparisons with $] to use numeric comparison instead

The fix follows Zefram's suggestion from
https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186846.html

> On older perls, however, $] had a numeric value that was built up using
> floating-point arithmetic, such as 5+0.006+0.000002.  This would not
> necessarily match the conversion of the complete value from string form
> [perl #72210].  You can work around that by explicitly stringifying
> $] (which produces a correct string) and having *that* numify (to a
> correctly-converted floating point value) for comparison.  I cultivate
> the habit of always stringifying $] to work around this, regardless of
> the threshold where the bug was fixed.  So I'd write
>
>     use if "$]" >= 5.014, warnings => "non_unicode";


  Commit: 8440144acfb5660ed849c300b29db4969a81800a
      
https://github.com/Perl/perl5/commit/8440144acfb5660ed849c300b29db4969a81800a
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M cpan/HTTP-Tiny/lib/HTTP/Tiny.pm

  Log Message:
  -----------
  [HTTP-Tiny] fix string comparisons with $] to use numeric comparison instead

The fix follows Zefram's suggestion from
https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186846.html

> On older perls, however, $] had a numeric value that was built up using
> floating-point arithmetic, such as 5+0.006+0.000002.  This would not
> necessarily match the conversion of the complete value from string form
> [perl #72210].  You can work around that by explicitly stringifying
> $] (which produces a correct string) and having *that* numify (to a
> correctly-converted floating point value) for comparison.  I cultivate
> the habit of always stringifying $] to work around this, regardless of
> the threshold where the bug was fixed.  So I'd write
>
>     use if "$]" >= 5.014, warnings => "non_unicode";


  Commit: 1e1a9b249b78e19fcaf85374822ef9476e5b1cd2
      
https://github.com/Perl/perl5/commit/1e1a9b249b78e19fcaf85374822ef9476e5b1cd2
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M cpan/Pod-Simple/lib/Pod/Simple.pm
    M cpan/Pod-Simple/lib/Pod/Simple/BlackBox.pm
    M cpan/Pod-Simple/lib/Pod/Simple/DumpAsXML.pm
    M cpan/Pod-Simple/lib/Pod/Simple/HTML.pm
    M cpan/Pod-Simple/lib/Pod/Simple/RTF.pm
    M cpan/Pod-Simple/lib/Pod/Simple/XMLOutStream.pm
    M cpan/Pod-Simple/t/ascii_order.pl
    M cpan/Pod-Simple/t/encod04.t

  Log Message:
  -----------
  [Pod-Simple] fix string comparisons with $] to use numeric comparison instead

The fix follows Zefram's suggestion from
https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186846.html

> On older perls, however, $] had a numeric value that was built up using
> floating-point arithmetic, such as 5+0.006+0.000002.  This would not
> necessarily match the conversion of the complete value from string form
> [perl #72210].  You can work around that by explicitly stringifying
> $] (which produces a correct string) and having *that* numify (to a
> correctly-converted floating point value) for comparison.  I cultivate
> the habit of always stringifying $] to work around this, regardless of
> the threshold where the bug was fixed.  So I'd write
>
>     use if "$]" >= 5.014, warnings => "non_unicode";

Note that, because some of the files do a `use integer`, the numeric
comparisons with $] a `no integer` needs to be done in a lexical scope
around the comparison, to avoid truncation to integers, which spoils
the comparisons. Hence the ugly `do { no integer ; ... }` in some places.


  Commit: 58aaa5e1f889924b27e2486f4a270ee46b80deda
      
https://github.com/Perl/perl5/commit/58aaa5e1f889924b27e2486f4a270ee46b80deda
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M cpan/Scalar-List-Utils/t/stack-corruption.t
    M cpan/Scalar-List-Utils/t/sum.t
    M cpan/Scalar-List-Utils/t/uniq.t
    M cpan/Scalar-List-Utils/t/uniqnum.t

  Log Message:
  -----------
  [Scalar-List-Utils] fix string comparisons with $] to use numeric comparison 
instead

The fix follows Zefram's suggestion from
https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186846.html

> On older perls, however, $] had a numeric value that was built up using
> floating-point arithmetic, such as 5+0.006+0.000002.  This would not
> necessarily match the conversion of the complete value from string form
> [perl #72210].  You can work around that by explicitly stringifying
> $] (which produces a correct string) and having *that* numify (to a
> correctly-converted floating point value) for comparison.  I cultivate
> the habit of always stringifying $] to work around this, regardless of
> the threshold where the bug was fixed.  So I'd write
>
>     use if "$]" >= 5.014, warnings => "non_unicode";


  Commit: aef568b32aae229df35c7471901f4647c6cca1b7
      
https://github.com/Perl/perl5/commit/aef568b32aae229df35c7471901f4647c6cca1b7
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M cpan/Test-Harness/lib/TAP/Harness.pm

  Log Message:
  -----------
  [Test-Harness] fix string comparisons with $] to use numeric comparison 
instead

The fix follows Zefram's suggestion from
https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186846.html

> On older perls, however, $] had a numeric value that was built up using
> floating-point arithmetic, such as 5+0.006+0.000002.  This would not
> necessarily match the conversion of the complete value from string form
> [perl #72210].  You can work around that by explicitly stringifying
> $] (which produces a correct string) and having *that* numify (to a
> correctly-converted floating point value) for comparison.  I cultivate
> the habit of always stringifying $] to work around this, regardless of
> the threshold where the bug was fixed.  So I'd write
>
>     use if "$]" >= 5.014, warnings => "non_unicode";


  Commit: ad1efdfec8f444d97a5e36a8285b48ba0551d1d5
      
https://github.com/Perl/perl5/commit/ad1efdfec8f444d97a5e36a8285b48ba0551d1d5
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M cpan/version/t/coretests.pm

  Log Message:
  -----------
  [version] fix string comparisons with $] to use numeric comparison instead

The fix follows Zefram's suggestion from
https://www.nntp.perl.org/group/perl.perl5.porters/2012/05/msg186846.html

> On older perls, however, $] had a numeric value that was built up using
> floating-point arithmetic, such as 5+0.006+0.000002.  This would not
> necessarily match the conversion of the complete value from string form
> [perl #72210].  You can work around that by explicitly stringifying
> $] (which produces a correct string) and having *that* numify (to a
> correctly-converted floating point value) for comparison.  I cultivate
> the habit of always stringifying $] to work around this, regardless of
> the threshold where the bug was fixed.  So I'd write
>
>     use if "$]" >= 5.014, warnings => "non_unicode";


  Commit: 24b25abf3b674d14301750f1758f2d6c2b91d806
      
https://github.com/Perl/perl5/commit/24b25abf3b674d14301750f1758f2d6c2b91d806
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M lib/perl5db.pl

  Log Message:
  -----------
  fix perl5db.pl to import the correct feature bundle


  Commit: 31e47f2ca2c3c39ec0c16f454edc75f688d37362
      
https://github.com/Perl/perl5/commit/31e47f2ca2c3c39ec0c16f454edc75f688d37362
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M t/comp/require.t

  Log Message:
  -----------
  fix require tests: all versions up to 41.7 are valid


  Commit: 7886c9dc95f2da9e084babbb4105d00566c817b3
      
https://github.com/Perl/perl5/commit/7886c9dc95f2da9e084babbb4105d00566c817b3
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M pp_ctl.c
    M t/comp/use.t

  Log Message:
  -----------
  fix use tests: all versions up to 41.7 are valid

use-ing these versions will load the :5.41 bundle, since that's
the highest one before them.

This also means that we don't need to give hints about why
'use 5.6' or 'use 5.10' fail, because they won't anymore.


  Commit: dbfe1223ce41e3133d00de902f1255a336970bf2
      
https://github.com/Perl/perl5/commit/dbfe1223ce41e3133d00de902f1255a336970bf2
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M ext/XS-APItest/t/xsub_h.t

  Log Message:
  -----------
  fix XS-APItest test about Perl API version


  Commit: 0397ab8b8d727f9d9885018f07ff3cbd0bcd00fd
      
https://github.com/Perl/perl5/commit/0397ab8b8d727f9d9885018f07ff3cbd0bcd00fd
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M lib/B/Deparse-core.t
    M lib/B/Deparse.t

  Log Message:
  -----------
  fix B::Deparse tests


  Commit: 05a12918ee8b790b8d9402ed7ca5bef2b071515c
      
https://github.com/Perl/perl5/commit/05a12918ee8b790b8d9402ed7ca5bef2b071515c
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M op.c
    M pp_ctl.c
    M t/lib/feature/implicit
    M t/lib/warnings/op
    M t/lib/warnings/pp_ctl
    M t/op/goto.t
    M t/porting/deprecation.t

  Log Message:
  -----------
  update fatal deprecation messages with the new version scheme


  Commit: 75941c336b154303224839940e84eece211d6c2a
      
https://github.com/Perl/perl5/commit/75941c336b154303224839940e84eece211d6c2a
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M regen/regen_lib.pl

  Log Message:
  -----------
  fix perl_version in regen/regen_lib.pl


  Commit: cfb495afe308e9d46567343b0dafbf210d7e806d
      
https://github.com/Perl/perl5/commit/cfb495afe308e9d46567343b0dafbf210d7e806d
  Author: Philippe Bruhat (BooK) <b...@cpan.org>
  Date:   2025-01-09 (Thu, 09 Jan 2025)

  Changed paths:
    M dist/Module-CoreList/lib/Module/CoreList.pm
    M dist/Module-CoreList/lib/Module/CoreList/Utils.pm
    M lib/B/Op_private.pm

  Log Message:
  -----------
  fix Module-CoreList to support versions larger than 5

Important fixes include:
* sorting numerical versions using <=>
* properly computing the family for versions larger than 5


Compare: https://github.com/Perl/perl5/compare/b104cb0de8be...cfb495afe308

To unsubscribe from these emails, change your notification settings at 
https://github.com/Perl/perl5/settings/notifications

Reply via email to