i'm beginning to think there should be optional warnings for goto
usage. perhaps use warnings 'goto'; could warn on goto LABEL and goto
EXPR, but pass goto &NAME.
I think that is a very bad idea. Warnings are there to prevent programmers
from making accidental mistakes. Warnings are done if
variables have unexpected values (comparing integers with ==,
adding undefined values, dereferencing non-references), when you try
to do something that cannot be done (open a bi-directional pipe), use a
deprecated feature (implicite @_), or did something you probably didn't
want to do (exiting eval with next, mying the same
variable twice in the same context</code>), etc, etc.
But the use of goto is not deprecated, and you will not get
much support to get it deprecated. And it's hardly likely someone types
goto by accident.
Warning should be used to prevent programmers from making mistakes -
as soon as warnings will be misused to force a coding style upon
programmers, use of use warnings and -w
will plummit - and rightly so. Forcing a coding style, one way or the
other, upon something else is Pythonesque.
Abigail
-
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.
|
