in this case it should ideally throw some error...
Further to Laurent_R's reply: If jabirahmed really wants to make these missteps into (fatal) errors rather than just having them generate nagging warnings, that can also be done. See perllexwarn. (Note that this control of fatality is lexical!)
>perl -wMstrict -le
"print 4 + 'a';
;;
use warnings FATAL => 'numeric';
print 5 + 'b';
"
Argument "a" isn't numeric in addition (+) at -e line 1.
4
Argument "b" isn't numeric in addition (+) at -e line 1.
>perl -wMstrict -le
"print 4 + 'a';
;;
use warnings FATAL => 'all';
print 5 + 'b';
"
Argument "a" isn't numeric in addition (+) at -e line 1.
4
Argument "b" isn't numeric in addition (+) at -e line 1.
(Many Perlers favor escalating 'all' warnings to fatality. I tend to agree with this practice, especially for modules, both OO and non-OO. However, I must admit that such fatality can get annoying during debugging.)
-
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.
|
