This is actually for systems that don't support shebang execution.

If you look very carefully, you'll notice that the eval string is a shell command, not Perl. On systems that don't have shebang, this gets handed to a shell, which hopefully has Perl in its PATH. That shell then exec's perl -S script args where the name was $0 and the args, if any, came from the ${1+"$@"}.

Now, when it does get handed to Perl, the if 0 on the next line stops it from doing the eval (of course, the shell is line-oriented and never sees the if!) This would also happen if the system started supporting shebang execution and the file was handed to Perl directly in the first place.

Nasty but effective, no?

In reply to Re: #! question by VSarkiss
in thread #! question by rbc

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.