comment on

Yeah. If you put it like this I agree completely. The whole problem I have with your post is that you blame Indigostar for the first two. They did not make it clear enough that the 1st is not real (but they never claimed it is), and they do say the result will "run at about the same speed".

You should not hold them responsible for someone elses faults. IMO of course.

You are right that with PAR being available there is no real reason to use Perl2exe anymore. It was a valuable tool (though I did not use it myself. I use PerlApp and PerlCtrl) but now there is an opensource replacement.

Anyway ... if someone asks me how to "covert a Perl script into an executable" I will mention PAR, PerlApp and perl2exe. It's his duty to choose, not mine. All I can do for him is to tell him that these three do the same thing just a little bit differently.

Jenda

In reply to Re: •Re: Re: perl2exe - no more secrets by Jenda
in thread perl2exe - no more secrets by merlyn

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.


The stupid question is the question not asked
	PerlMonks