GS>>Well, point a) implied that it's a solvable problem, at least as much as it GS>>is when doing any sort of premature exit from a block.
It's worse problem since we are going to jump to random place and not just to the end of the block. At the end of the block we could have opcode that takes care of that. At random place, we can't have it. GS>>Isn't ignoring memory leaks the official (tm) strategy for using GS>>exceptions in PHP5 though? :) Never heard of it. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
