comment on

I guess you are the same anon Monk who wrote:
perlapp --add DateTime::** ... foo.pl

No I didn't test that. However, it looks like it would work.

As I explained, I prefer to modify the source code so that this "--add" option is unnecessary. This has the benefit of eliminating one extra piece of info to keep track of! After the usual activity around the first release, some of my apps can run for 4-5 years before I get a bug report or feature request. A lot can change over the years (Perl version, PerlApp version, other dev environment things, predominate user platform, etc). If I have to revisit a piece of code, I will rebuild the .exe using the latest Perl and Perlapp versions and of course use my QA testing process. If perlapp just runs without requiring any special options, so much the better for me.

BTW, I don't use the Perlapp command line anymore. Run the GUI by just hitting CR after PerlApp.

At the end of day, there is more than one way to solve this problem. I have good reasons based upon 20 years of experience for why I do what I do. However this doesn't have to be a "one size fits all" situation.

In reply to Re^3: Active perl Perlapp problem by Marshall
in thread Active perl Perlapp problem by harryC

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.