"Basically, prototypes are not for catching errors at compile time. Rather, they're for changing the precedence of the subroutine calls."
% perl -le 'sub f ($) { print @_ } f(1, 2)' Too many arguments for main::f at -e line 1, at end of line Execution of -e aborted due to compilation errors. % perl -le 'sub f ($) { print @_ } f()' Not enough arguments for main::f at -e line 1, at end of line Execution of -e aborted due to compilation errors.

Prototypes have been catching errors of this sort since 5.002.

hdp.


In reply to Re: (bbfu) (prototype misconception) Re(2): Declaring Subroutines (predeclare, catch errs at compiletime?) by hdp
in thread Declaring Subroutines by the_0ne

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.