I find that if my app grows I invariably end up doing the following. (Ususally I need my stuff to run in Win32 and Solaris)
- Kick off the perl script with a bat script with the same name as a shell script and available via normal system paths. ( That way both have the same command line)
- Use the bat/shell script to set local library locations and cd to the root of the application/scripts
- (After my command line parsing) a begin block to get my libraries to load the way I want/need them to
- Pull in a config file that utilizes relative directories to load into the environment (%ENV).
While this isn't optimal, it is reliable and reuaable, and has become so much a pattern I just start with this style from a template (which includss generic POD and of course strict & -w )
Unfortunately the company has laid ownership to the template, but it is easy enough to roll your own
-
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.
|