was written to solve a slightly different problem than Inline
. The api is simpler, and better suited for translation based operations (like source filters) than interfacing foreign runtimes with additional precompilation, mostly via introduction of symbols as alias for foreign functions (by overriding load or relying on DynaLoader). For these reasons Module::Compile is more appropriate. Also, Inline
's caching is not based on Perl's .pmc infrastructure, so shipping cached code is trickier.
Note that the one of the authors of Module::Compile is also the author of Inline.
Short answer: Inline::TT would be ~ 5x the amount of work that Module::Compile::TT was.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.