> > Hacks often adversely affect maintainability of any given > > system. For example, the computed goto hack relies on > > separate definitions of all opcodes. Failing to keep this > > list up to date can result in subtle, hard to diagnose > > failures which is undesirable for a stable system (PHP 4). > > As if the list of opcodes is likely to change in PHP 4. That sounds like > a bogus argument to me.
Rasmus, that was one example (zend_gc.c), not the argument (negative effect on maintainability). You really should know the difference. Regardless, to move the discussion forward, the patch contains a number of interesting concepts. Maybe Sterling/Thies could split them up and make them available for review, if they consider them to be stable enough for inclusion. - Sascha -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php