-- is how you'd generally denote options for something else other than the first executable that's being called.

For example for perl, perlrun says that: A -- signals the end of options and disables further option processing. Any arguments after the -- are treated as filenames and arguments..

What this means roughly, IIRC, is that you use it to pass of options after -- to the perl script you're calling with perl.

For example,

$ perl -MSome::Module ./myperlscript.pl -- --my-opt1 foo --my-opt2 bar
[download]

What this also means, I think, is that it's useless when part of the shebang line. Or maybe not, idk. Seems odd being in the shebang, though.

Update - after thinking about it, I can see how this might be considered a defensive programming tactic. E.g., if somehow some script kiddie was seeking the add options to your shebang, having -- would make anything after moot. Similarly, adding __END__ at the end of your perl scripts would also neutralize someone blindly appending to your files.

---

---

• 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.