I know the call to ivadmin_context_createdefault() isn't working because ivadmin_response_getok is saying so. And, since the identical code works as a C program, I know it isn't my call to the library.

The PREFIX option on the use Inline C line causes perl to "strip" that prefix from the function as defined in the C code. Thus, I define it as my_create_context in the C code, and use it as create_context in the perl code.

Upon reading the docs a bit closer, if Inline didn't like the return type from my_context_create, it would simply ignore the function. As I can call it from perl, I assume this isn't the problem. Again, if I read the docs right, I don't need a typemap unless I intend on using one of those structs as a return type.

I tried your suggestion on the update, and it is saying the function has been bound to perl. I have also browsed the generated XS code and it looks correct to me, although I think I indicated previously that my XS skills are nonexistent.

I am using the same make.

Thanks for the suggestions, Ovid. I am back to hitting the docs and trying ( once again ) to work my way through perlapi.

mikfire

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.