Re: GOTO operator
| From: | Andrey Hristov | Date: | Thu, 19 Aug 2004 06:58:08 +0000 |
| Subject: | Re: GOTO operator | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-12252@lists.php.net to get a copy of this message | ||
Is it good idea (and is it possible) to disallow GOTO in main() ?
Andrey
Quoting Robert Cummings <robert@interjinn.com>:
> On Wed, 2004-08-18 at 21:34, BDKR wrote:
> > Hartmut Holzgraefe wrote:
> >
> > > Sebastian Bergmann wrote:
> > >
> > >> Exceptions are not an OOP feature per-se. They are a means for out-of-
> > >> band error signalling. (Of course they use objects for that which could
> > >> be regarded as a turn-off by non-OOP-eople :-)
> > >
> > >
> > > they can also be a turn-off for performance anxious people
> > >
> > >
> > Perhaps I missed it somewhere in the proceedings, but what is the
> > current thinking on goto / label implementation in PHP? Sorry if there
> > was a decision made and I just missed it. :-(
>
> The general consensus was in favour of GOTO with labels with the
> following restrictions:
>
> - compile time hooking (no dynamic goto targets)
> - goto can only jump to labels within the same scope
> - goto could only jump out of blocks and not into
>
> Cheers,
> Rob.
> --
> .------------------------------------------------------------.
> | InterJinn Application Framework - http://www.interjinn.com |
> :------------------------------------------------------------:
> | An application and templating framework for PHP. Boasting |
> | a powerful, scalable system for accessing system services |
> | such as forms, properties, sessions, and caches. InterJinn |
> | also provides an extremely flexible architecture for |
> | creating re-usable components quickly and easily. |
> `------------------------------------------------------------'
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>