If you think it's worth the effort, try changing (in util.c)...
I don't think it's worth the effort.
I thought it might be useful to see what happens on your system if the handshake fails but the program is allowed to continue on.
So I tried (on Windows) changing the "noperl_die" to a "Perl_warn" as I suggested above, but when faced with an XS.dll (from an earlier version of perl) that failed to pass the handshake, the program still died:
XS.c: loadable library and perl binaries are mismatched (got handshake
+ key 00000000005487e8, needed 0000000000000000)
Even making util.c's Perl_xs_handshake() return as soon as the handshake mismatch was detected didn't prevent the fatality.
I was hoping for a simple, unsophisticated, way of turning the mismatch into nothing more than a warning - but the gestapo have got me snookered on that one ... for the moment, anyway.
It probably wouldn't have helped much, anyway.
Cheers,
Rob
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.