But I get annoyed when it stops me from running some small piece of Inline::C code that would (I believe) have executed perfectly well if the failing handshake check had not killed itAs an example of why that's not necessarily true, consider a simple XSUB which returns a value. It may return that value using a PADTMP, or it might return it as a mortal SV, which (behind the scenes) pushes a value onto the temps stack and updates the stack index. Between Perl 5.18 and 5.20, the type of the temps stack index changed from 32-bit to 64-bit. A "simple" XSUB compiled under 5.18 and run under 5.20 may well cause the interpreter to SEGV soon after returning.
Yes, sometimes you might get lucky. But I think the use cases for disabling the check are rare enough that its not worth adding such a feature.
Dave.
In reply to Re^5: How do I build perl on Windows such that all "handshake" checks are avoided ?
by dave_the_m
in thread How do I build perl on Windows such that all "handshake" checks are avoided ?
by syphilis
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |