Why rewrite your Perl code in C?? Just because you have some XS code doesn't mean you have to do every single thing for that module in XS code!
Do in C, only the stuff that is easy in C. Use a wrapper subroutine written in Perl to do stuff like what you are trying above. The code you have above is the kind of code that breaks when a new version of Perl comes out (or doesn't work when someone tries to use it on an older version of Perl than the one you developed it on).
I've done this quite a bit and have been extremely happy with the results. I find I can make modules with much nicer, Perlish interfaces than I see in other XS modules. Plus the code ends up being much easier to understand, maintain, enhance, and debug.
-
tye
(but my friends call me "Tye")
-
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.
|