Yes, I flip-flopped between thinking that all of the functions used u_char **buf and thinking what you just described. So parts of what I wrote may be a bit confusing (sorry, and more on this later). But my final analysis is correct based on what you write above.

You need to have all of the functions use u_char *buf or u_char * &buf and nothing else. The typemap defines a way to convert between a u_char * and a Perl UV (unsigned long integer). The & tells XS to use &buf as the argument to the function. So you specify the & when the function expects u_char **buf.

Where you quote me above, I have quoted code that shows that XS is trying to convert to/from a Perl PV (string) instead of a UV. This probably means that you used char *buf instead of u_char *buf. So what I wrote wasn't due to confusion about whether buf was a pointer or a pointer-to-a-pointer for that case.

You do need to use the same typemap (u_char *) for all of the functions. It is just that some also need the & as well.

The Perl variable, $buf, will hold an unsigned integer value that is the value of the u_char * pointer (just typecasted).

Does that make more sense?

        - tye (but my friends call me "Tye")

In reply to (tye)Re6: XS question: typemap for a pointer to a pointer? by tye
in thread XS question: typemap for a pointer to a pointer? by Big Willy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.