Perl 5 Porters Mailing List Summary: August 22nd-28th

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week. Enjoy!

August 22nd-28th

News and highlights

Threads::Semaphore was upgraded in core to 2.13.

Grant reports


New issues

  • Perl #129048: lib/perlbug.t: avoid spurious failure when testing long PATH line.
  • Perl #129059: lexical subs - my sub using our sub segfaults.
  • Perl #129061: Valgrind: Buffer overrun in S_regmatch with pathological regular expression.
  • Perl #129068: SV *Perl_cv_const_sv_or_av: Assertion fail.
  • Perl #129069: Fuzzer-detected use-after-free in Perl_yylex.
  • Perl #129070: Refactor toke.c into smaller, more maintainable parts.
  • Perl #129071: Perl git repository not available over HTTPS.
  • Perl #129072: Typo in perlpodspec.
  • Perl #129073: Perl_yyparse: Assertion fail.
  • Perl #129087: Null ptr deref, segfault Perl_sv_setsv_flags.
  • Perl #129090: Perl_pad_fixup_inner_anons Null reference Memory corruption.
  • Perl #129098: Perl should have a cycle detector.
  • Perl #129106: null ptr deref, segfault Perl_sv_vcatpvfn_flags (sv.c:12398).

Reopened issues

This week a ticket was reopened because it was not yet resolved in blead.

  • Perl #129067: Use of inherited AUTOLOAD for non-method is deprecated.

Resolved issues

Rejected issues

  • Perl #129105: null ptr deref, segfault Perl_newSVpv (sv.c:9218).

Suggested patches

Dan Collins provided a patch in Perl #129058 ([PATCH] Perl_do_vop: resulting string isn't always null-terminated), relating to null-terminated strings.

Theo Buehler provided a patch in Perl #129102 (to update the man pages links for strlcat and strlcpy).


Aristotle Pagaltzis provided an improvement of the original patch change to by Peter Rabbitson (Ribasushi). Another suggestion, raised by Todd Rinaldo, is to leave the module unchanged. This is supported by Peter, Aristotle, and Kent Fredric.

Martin Dyers raised ( a question about the licensing of Data::Dumper which does not contain its own license file. Should we add a file to each or should we just document the license in the POD?

Father Chrysostomos provided comments regarding the utf8 warnings in Encode.

Herbert Breunung asked for suggestion on documentation Pod files that could use help cleaning up, fixing, or generally improving.

1 Comment

Good weekly job! thanks.

Leave a comment

About Sawyer X

user-pic Gots to do the bloggingz