I disagree, I find PerlApp invaluable. I have many Win32 machines that are regularly re-imaged, and trying to keep modules and perl versions up to date and in sync on those machines is more work than it is worth, having .exe's lets me just copy a tools directory over, put it in the path and use them. That is a much easier script to write than trying to sync all my version #'s.
And, if your going to allow users to play with these, in the .exe all of your scripts are always being run with the same version of perl, the same version of each module, etc...makes debuging user issues easier, and avoids many user support issues in the first place.
If you are going to put the tools up for download (for a legitimate reason :) making them .exe's makes support much easier.
"Nothing is sure but death and taxes" I say combine the two and its death to all taxes!
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.