Branch: refs/heads/parsexs-length-t_pv
  Home:   https://github.com/Perl/perl5
  Commit: 7c58ce3da0a7371e2561ef08ca19546dc93550af
      
https://github.com/Perl/perl5/commit/7c58ce3da0a7371e2561ef08ca19546dc93550af
  Author: Leon Timmermans <faw...@gmail.com>
  Date:   2025-07-27 (Sun, 27 Jul 2025)

  Changed paths:
    M dist/ExtUtils-ParseXS/Changes

  Log Message:
  -----------
  Pull in ExtUtils::ParseXS Changes file from CPAN


  Commit: 975d8393e11814c68ef5ed5c03040acc290ba695
      
https://github.com/Perl/perl5/commit/975d8393e11814c68ef5ed5c03040acc290ba695
  Author: Leon Timmermans <faw...@gmail.com>
  Date:   2025-07-27 (Sun, 27 Jul 2025)

  Changed paths:
    M dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/Constants.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/CountLines.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/Eval.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/Node.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/Utilities.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/Cmd.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/InputMap.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/OutputMap.pm
    M dist/ExtUtils-ParseXS/lib/ExtUtils/Typemaps/Type.pm
    M dist/ExtUtils-ParseXS/lib/perlxs.pod

  Log Message:
  -----------
  Bump ExtUtils::ParseXS to 3.59


  Commit: ba4e8e054afb8d31ddcf04762abdc428e77eac48
      
https://github.com/Perl/perl5/commit/ba4e8e054afb8d31ddcf04762abdc428e77eac48
  Author: Leon Timmermans <faw...@gmail.com>
  Date:   2025-07-27 (Sun, 27 Jul 2025)

  Changed paths:
    M dist/ExtUtils-ParseXS/Changes
    M dist/ExtUtils-ParseXS/lib/ExtUtils/ParseXS/Node.pm
    M dist/ExtUtils-ParseXS/t/001-basic.t

  Log Message:
  -----------
  Explicitly length(NAME) with typemaps other than T_PV

Previously, the length operator on typemaps other than T_PV would lead
to that length value not being initialized, leading to segfaults and
worse. Worse yet, parsexs would silently emit this erroneous code.

For now it will at least give a clear error, in the future we should
perhaps consider eliminating this limitation altogether.


Compare: https://github.com/Perl/perl5/compare/c0ba3a9795a4...ba4e8e054afb

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

Reply via email to