Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Curiously, I'm wrestling with this very issue right now. This approach just isn't any good unless you can be sure that the Perl in the shebang line has all the same mods installed as the custom installs you're trying to execute. We have a Perl script that we require in a BEGIN block for each script we run, and we'd have to both make sure that the #!/usr/bin/perl has all of the mods that we're using in the script otherwise it won't compile, and we'd also have to evaluate the require once for the #!/usr/bin/perl and then again for the script running under the correct Perl.

In reply to Re^2: different exe path for different OS by bergbrains
in thread different exe path for different OS by bharatbsharma

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.