I think Sriram's advice in A.P.P.1 should be considered very out-of-date.
1997: Advanced Perl Programming (First Edition) by Sriram Srinivasan
Pages on SWIG: 5, XS: 4, Both: 8, Inline: 0.
SWIG underwent a major rewrite between 1999 and 2001.
2002: Extending and Embedding Perl by Tim Jenness and Simon Cozens
Pages on SWIG: 6, XS: 200+, Inline: 10.
2005: Advanced Perl Programming (Second Edition) By Simon Cozens
Complete rewrite, with little overlap from the First Edition.
One whole chapter on Inline.
From A.P.P.2 - "Packaging Inline Modules":
In the past I'd always seen Inline::C as useful for prototyping, or a simple glue layer between C and Perl for quick hacks, and would discourage people from using it for the "serious" business of creating CPAN modules.
However, Brian "Ingy" Ingerson has worked hard on these issues and there are now two equally suitable ways to write fully functional Perl modules in Inline, without bothering with XS.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||