hmm ...can't reproduce!
For me both cases are consistent and throw warnings instead of dieing
perl -version
This is perl, v5.10.0 built for i486-linux-gnu-thread-multi
code:
BEGIN {
$SIG{__WARN__}=sub { print "WARNING: $_[0] \n" };
}
$|=1;
sub fn1($);
fn1("output1");
sub fn1 (\@) {
print while $_ = shift;
}
sub fn2($);
fn2("output2");
sub fn2 (\@) {
print $_,$/ for @_;
}
output:
$ perl /tmp/proto.pl
WARNING: Prototype mismatch: sub main::fn1 ($) vs (\@) at /tmp/proto.p
+l line 11.
WARNING: Prototype mismatch: sub main::fn2 ($) vs (\@) at /tmp/proto.p
+l line 18.
output1output2
If you want it do die try to catch the /^Prototype mismatch:/ in $SIG{__WARN__}.¹
Cheers Rolf
( addicted to the Perl Programming Language)
UPDATE
¹) or check if categories in warnings help defining "Fatals" on "Prototype mismatch".
-
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.
|