Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: GOTO considered (a necessary) evil?

by Abigail-II (Bishop)
on Jul 15, 2002 at 16:14 UTC ( #181841=note: print w/ replies, xml ) Need Help??


in reply to Re: GOTO considered (a necessary) evil?
in thread GOTO considered (a necessary) evil?

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


Comment on Re: GOTO considered (a necessary) evil?
Select or Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://181841]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (4)
As of 2014-12-22 05:08 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (110 votes), past polls