4

NO_XSLOCKS allows the usage of some error checking macros in XS code when combined with #include XSUB.h. However, its use seems to go beyond that. It was recently suggested that I add it to my XS file for better compatibility with ActiveState perl, with this issue given as an example.

What else does #define NO_XSLOCKS do, and when should I use it in my XS code?

Marco Bonelli
  • 63,369
  • 21
  • 118
  • 128
Nate Glenn
  • 6,455
  • 8
  • 52
  • 95
  • 1
    You have to define `NO_XSLOCKS` if you want to use the [`XCPT_*` macros](http://perldoc.perl.org/perlguts.html#Exception-Handling) for excpetion handling. Additionally `NO_XSLOCKS` disables the replacement of C library functions with Perl wrappers. I have no idea why the same macro is used for seemingly different things, and where its name comes from. Adding a bounty to hopefully attract some attention. – nwellnhof Mar 12 '15 at 15:00
  • http://www.tagwith.com/question_569899_when-should-i-define-no-xslocks –  Mar 19 '15 at 14:48
  • @HaltlolXD Why did you post that? That his his exact question posted on another site. – Jared Burrows Mar 19 '15 at 14:55
  • Yes, and I am also wondering this, so keep an eye on both ;) @JaredBurrows –  Mar 19 '15 at 14:58
  • I should have been more clear. Look at the dates, posted same day, relatively the same time. This post is the original and "tag with.com" simply scans the web for this kind of content. That is why I asked "why did you post this?" – Jared Burrows Mar 19 '15 at 15:06

0 Answers0