comment on

It's not really clear if the OP has a question or is just musing. Sounded more like musing over what might be a good approach for standlone perl apps -- but there are really two separate issues that should be kept distinct:

Packaging up a perl script with an interpreter to run as a standalone
Storing the compiled perl bytecode so the source isn't recompiled each time

PAR is only an answer to the first, I think. The OP seemed a bit more focused on the second. I'm not sure how much speed gain that really gives, though. It all comes down to the ratio of compile time versus run time. For user apps, I don't know that compile time matters so much.

For the second, mod_perl and PersistentPerl are a couple of approaches used to address this with a persistent perl interpreter.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

In reply to Re^2: Doing a standalone executable (and even a binary!) by xdg
in thread Doing a standalone executable (and even a binary!) by Ace128

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 or How to display code and escape characters are good places to start.


go ahead... be a heretic
	PerlMonks