Re: GOTO operator
| From: | Alex Pagnoni | Date: | Fri, 30 Jul 2004 08:12:10 +0000 |
| Subject: | Re: GOTO operator | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-11657@lists.php.net to get a copy of this message | ||
Alle 04:04, venerdì 30 luglio 2004, hai scritto:
> Where do you see the correlation between OOP and the presence/absence of
> "goto"?
It is not for the OOP model by itself, but for a general code maintenability
issue that OOP languages tend to address, while a too powerful goto operator
may cause certain abuses from not well experienced programmers.
Being involved in the open source world, I frequently have to deal with
other's code. I hope not to find a day a project that I have to internally
deal with, containing a jungle of gotos.
It is a sort of strategical decision - while it seems to me that with the new
ZE the PHP language is suggesting the path for a more and more (hopefully)
maintenable code, it seems also that with a goto operator we also allow to
produce less even maintenable code.
But reading the various posts here, I changed a little my opinion. I'm in
favor of a goto operator if the "scope" of its labels is limited to, say, a
function/method only. My experience with basic is dated at about twenty years
ago so in my mind there are ugly examples like 10 print / 20 goto 10 :-)
So now I can give, as others said, my +0.00000001.
Alex