Hello, I represent group B (not in any way officially or anything else
that might give my words an iota of weight), but I (*cough cough*) WE
think that the above break system would make a terrible system for
finite state machines.
Good, 'cause that's not its purpose. This doesn't supplant GOTO or preclude
it. This is a different topic about a different feature which just happens
to touch on SOME similar talking points.
Additionally at this time I'd like to make clear that we are in support
for full uncrippled break WITHIN scope. Group A can feel free to travel
to the burning fires of hell and have a barbecue, and group C should
join us so that at least they get what they want as a subset.
Lead on the charge good sir... lead on.
As an aside, from what I've read, the multitude were in favour of
unrestricted goto. Quite a few were in favour of none at all (but not as
many as in group B) and those in favour of none at all had a large
subset that were in favour of unrestricted goto in the event that group
B should get their way :)
Not to put too fine a point on it, but there's a limited subset of the
voices on this list that carry the weight needed to push a feature like goto
into the engine. Amongst those voices there is a much less decisive quorum.
-Sara
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
