Looking at
rafl's explanation, I think I find it much simpler to avoid the
char** typemapping altogether, and pass the argument from perl to C as an
AV* rather than a
char**Here's a self-contained ultra-simplistic example (plagiarised from "Extending and Embedding Perl"):
use warnings;
use Inline C => Config =>
BUILD_NOISY => 1;
use Inline C => <<'EOC';
void foo(AV * avref) {
int i, len;
SV ** elem;
len = av_len(avref) + 1;
for(i = 0; i < len; i++) {
elem = av_fetch(avref, i, 0);
printf("%s\n", SvPV_nolen(*elem));
}
}
EOC
@strings = (
'hello',
'a string',
'another string',
'bye',
);
foo (\@strings);
Not sure if that helps at all ... I concede that it certainly doesn't answer the question you asked :-)
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.