You should have done the Perlish API stuff in wrappers written in
Perl that called the SWIG / XS / Inline::C wrappers.
As Joost said, it depends. In the project I was referring
to, SWIG simply didn't provide enough flexibilty to get the (sometimes
weird and dynamic) data structures converted into anything which would
have remotely made sense in Perl. In other words, doing this part in
Perl essentially would've meant returning big chunks of memory and then
fiddling with pack()/unpack() on the Perl side to create the objects as
needed. This certainly wouldn't have made it less fragile. Changing the
C side wasn't an option, as it was a closed source third party library.
Well, I don't want to go into further details. I'd just like to
point out that in the end, the flexibility of XS did allow me to write
less and faster, i.e. more-to-the-point code than SWIG did.
Ugh. The "cool" factor of writing ugly, fragile code.
Did you notice the smiley?
-
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.
|
