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.

Replies are listed 'Best First'.
Re: [Good news] here docs portability!
by Anonymous Monk on Jun 17, 2007 at 02:19 UTC
    this is not news
      Well, it was obviously news to blazar, and it's pretty certain to be news to a good many others too.

      And sudo ln -s /usr/bin/perl /usr/bin/perl`echo -e '\r'`

        Better make that /bin/echo...

        What was I thinking, qx// is executed with /bin/sh regardless of user's favorite shell.