Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Why? It's good system administration, that's why. As I said in my original post, "rolling the dice is for role-playing games, not work!" In other words, you do not leave things to chance for things running in production. If you cannot grasp that concept then you just do not have enough system administration experience. You may want to read some "best practices" type books, such as "The Practice of System and Network Administration 2nd Ed" (publisher and Amazon links). Or work in a shop with several other developers and multiple Perl installations for some hands on experience.

Your argument against a "fragile" wrapper script makes little sense because the entire system is "fragile". For example, you are concerned that an upgrade may break your wrapper script when an upgrade to the system will more likely break your Perl script.

Your argument against a big complicated wrapper script also does not hold water. If the environments your code may run in are that different then you are going to have to do something about it anyway. If not then it is not going to be a complicated script. You are also moving into the realm of distributing code where a build environment would be more appropriate. What do you think happens when you do a "perl Makefile.PL"? Or a "./configure"?? Someone else has spent time figuring out how to resolve environment related issues for you. Quite frankly, it sounds like you are used to using packages created by others and thus have not been exposed to the work that went into making them. Have you ever tried compiling Perl or GCC?

But at the heart of it all is that principle that you make sure you know what your production code is doing and what it is relying on.

Elda Taluta; Sarks Sark; Ark Arks

In reply to Re^3: #!/usr/bin/perl vs. -*- perl -*- by Argel
in thread #!/usr/bin/perl vs. -*- perl -*- by why_bird

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (1)
As of 2023-06-04 03:08 GMT
Find Nodes?
    Voting Booth?
    How often do you go to conferences?

    Results (17 votes). Check out past polls.