On Tue, 26 Aug 2003, Sascha Schumann wrote: > > > 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.
And I do, but you were the one who picked the example. I agree that hacks increase maintenance work, but you picked a particularly bad example of that suggesting that we would have on ongoing nightmare of keeping the opcode table in synch when in fact the opcode table is likely to never change in PHP4. In a stable codebase, where features are not being added anymore, performance-oriented hacks are quite appropriate. -Rasmus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
