comment on

I'm currently working on connecting Perl with C++ via XS, only I'm hitting a problem when it comes to typemaps.. or lack of same.

At the moment I'm handling C++'s method overloading with something with the following basic structure (plus extra error checking, removed here for clarity):

int
MyClass::countItemsIn (...)
  CODE:
    if (sv_derived_from(ST(0), 'MyList')) {
      RETVAL=THIS->countItemsIn(
        *(MyList *) SvIV((SV*)SvRV(ST(0)))
      );
    } elsif (sv_derived_from(ST(0), 'MyHash')) {
      RETVAL=THIS->countItemsIn(
        *(MyHash *) SvIV((SV*)SvRV(ST(0)))
      );
    }
  OUTPUT:
    RETVAL
[download]

..now I can happily write this kind of code, but what's worrying me is "Where are the typemaps?". If I were to do all of the conversions manually I'm a lot more likely to make mistakes, and basically mess it all up. I'm also considering wrapping things in a very different way so being able to change the effective mapping would be exceptionally useful.

What is the best way to approach this, is there a way to call typemap conversions as 'functions' in XS? If not, shall I wrap the XS code for the typemap conversion in a nice little method and call that?

EDIT: Changed wording slightly, this doesn't seem to be the 'best' version to me at all..

In reply to Terrible Trouble With Typemaps (XS Question) by Molt

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.


Welcome to the Monastery
	PerlMonks