From the reply to a post of mine in a clpmisc thread (link @ GG), both to the author's (Peter J. Holzer) and my own surprise:
>>If you don't convert the *script* (as opposed to print statements wi
+thin
>>the script), apache probably can't even start the script because the
>>linux kernel will try to invoke "/usr/bin/perl\r" which doesn't exis
+t.
>
> BTW: I've always wondered... how 'bout HERE docs? Are they portable
> across platforms or is the line ending deemed to be that of the
> script.
To my surprise they are portable at least between Unix and Windows. Pe
+rl
seems to automatically detect the line endings and convert them to
\x{0A} at compile time. A string written as a here document always
contains simple "\n" characters as line endings regardless of whether
the source file contained CRLFs or LF and whether it's executed on
Windows or Unix.
-
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.
|
