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.
-
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.
|