My problem with perl2exe (which you would see if you had super search'ed back) is that it gets tossed around as a solution to three problems:
- code hiding
- "speeding up" by "compilation"
- bundling for single-file installation and sharing
Well, the first two are bogus claims (especially since the exploits for the code hiding are now readily available). And the third was a nice feature, but is now completely satisfied by PAR.
But instead of making it clear that the first two were bogus claims, they continued to take $99 from unsuspecting souls. This borders on outright lack of ethics, as far I am concerned.
So, mostly on principle, I must continue to urge people to please stop recommending perl2exe. Use PAR.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
-
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.
|