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?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||