the problem is, that, in this case, code is not broken. it is not an error to use large stack. it is an error to let someone use the low-level side-effects of a problem in a high-level language.
On 5/21/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Well yes. I think to solve this "once and for all" a public statement by > the PHP group would be nice that says: I don't think they are "not important", just that they are not important enough to want them fixed no matter the cost. Running shared hosted server in a mode that relies on restricted code IMO is wrong anyway, and for non-shared environment these problems could be exploited only if specifically enabled by very badly written code. So when there's a trade-off between having the language work better for 100% of cases or protect those who run broken code on their servers - the choice would be to make language run better. Again, that doesn't mean bugs shouldn't be fixed - just the fix shouldn't make the situation worse. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- Alexey Zakhlestin http://blog.milkfarmsoft.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
