Front page | perl.perl5.porters |
Postings from July 2012
On Sun, 29 Jul 2012, bulk 88 (via RT) wrote: > > > Would it be possible to add the 2 patches (1 has been applied to > blead, the other hasn't been), in Thanks for mentioning the 2nd patch; I never saw email notifications that the bug had be re-opened. > https://rt.perl.org/rt3/Ticket/Display.html?id=114144 (and a regen.pl) > to the next 5.16? > > I categorize as a portability fix, and they do not affect ABI since > Win32 GCC Perls have been compiled with noreturn declaration for > years, code after a longjmp is unreachable by definition. Perl claims > to be ABI compatible Visual C Perl and Mingw GCC XS modules, see > http://www.perlmonks.org/?node_id=614808 , the other direction I am > not sure about. > > It will reduce about a dozen KB (in my experience) of unreachable > machine code in the perl dll, and also reduce the size of any XS code > compiled Visual C. > > I propose this because 5.18 is 10 months away, and 5.16 still has 21 > months on it. I don't see how this could possibly count as a portability fix; having a few KB of unreachable code is not a serious issue at all in my mind, so it does not fit the spirit of pod/perlpolicy.pod. Cheers, -JanThread Previous