Front page | perl.perl5.porters |
Postings from January 2022
On 2022-01-13 6:25 a.m., demerphq wrote: > On Thu, 13 Jan 2022 at 14:26, Sergey Aleynikov wrote: > For other's reference - it broke DBIX::Class > https://github.com/Perl/perl5/issues/17663, and you know it. It's > quite late in a release cycle to bring this up, since it'd require a > lot of efforts to release a fixed version of it to CPAN. > > Yeah, I get your point, so maybe we have to suffer one more release, but bottom > line if DBIx::Class depends on this bug then it is depending on clearly *broken* > behaviour, and you have to wonder what insanity is being hidden. I feel that Perl 5.36.0 SHOULD fix its own broken behavior regarding stack traces. Just don't fix it in any 5.34.x or 5.32.x etc. The 5.36.0 release is a major release and is far enough away that DBIx::Class should be able to get fixed to not rely on the broken behavior in time for its release. The fix shouldn't be put off another year. If anyone depends on something that depends on the broken behavior, they should not upgrade past 5.34.x until their other dependencies are updated for compatibility. -- Darren DuncanThread Previous | Thread Next