Well, the caller is the C call that's, um,
calling the perl code. As far as expectations go, I suppose initially that I naively expected Carp to report that, but of course that's not going to happen as it is.
Expectations aside, I would like to affect the same thing that Carp would normally do. The module is being used both from C and from Perl, so the solution must be general. Maybe I could subclass Carp so that it will report differently in the case of no call-stack (*now* maybe I'm answering my own question :^).
The whole thing with passing perl_parse() "/dev/null" feels less than clean as well. How is this normally handled?
Whatever I do, I was hoping to follow convention -- if there is any -- and that's why I'm laying this out here. What *do* folks do when they load_module() code that contains Carp?
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.