Re^3: Segmentation fault

Every CPAN module has "C/C++ (so called "XS") code"? Perhaps I don't know what I'm talking about, but aren't there "pure Perl" modules in CPAN that don't have any C/C++/XS code in them? (i.e. only Perl code)

Actually, after re-reading your wording, maybe I misunderstood you. Are you saying "every module in CPAN" has C/C++ code or are you just talking about the CPAN module itself that has C/C++ code?

Comment on Re^3: Segmentation fault

Replies are listed 'Best First'.
Re^4: Segmentation fault by locked_user sundialsvc4 (Abbot) on Jul 03, 2012 at 20:19 UTC
There are some “Pure Perl” packages out there, certainly. But if you’re getting a segmentation fault, you are definitely (directly or indirectly...) dealing with one that is not. Many Perl packages consist partially or entirely of “wrappers for” existing libraries. (e.g. XML::LibXML). Others (YAML::Syck) do it for speed. So, even though you as a Perl programmer are simply dealing with “a nice, well-behaved Perl package,” in the case of some packages there are lower-level calls being made under the hood. The source-code of the package therefore consists, not only of Perl code, but also C/C++ code and the necessary “plumbing” needed to connect one to the other. Just install the package in the usual way, and, presto, it all just happens. It’s kind of like Laws and Sausages: they work (well, sausages do, anyway), but you really don’t want to know how they’re made ...

Replies are listed 'Best First'.

Re^4: Segmentation fault
by locked_user sundialsvc4 (Abbot) on Jul 03, 2012 at 20:19 UTC

There are some “Pure Perl” packages out there, certainly. But if you’re getting a segmentation fault, you are definitely (directly or indirectly...) dealing with one that is not.

Many Perl packages consist partially or entirely of “wrappers for” existing libraries. (e.g. XML::LibXML). Others (YAML::Syck) do it for speed. So, even though you as a Perl programmer are simply dealing with “a nice, well-behaved Perl package,” in the case of some packages there are lower-level calls being made under the hood. The source-code of the package therefore consists, not only of Perl code, but also C/C++ code and the necessary “plumbing” needed to connect one to the other. Just install the package in the usual way, and, presto, it all just happens. It’s kind of like Laws and Sausages: they work (well, sausages do, anyway), but you really don’t want to know how they’re made ...