SF>>You'd need to be _dynamically_ loading somewhere over 24 modules for that to SF>>happen, and this is me testing with a --disable-all build. Normally it'd be
So what? What is so special in number 24 that it can never happen? 640K of memory is enough for everybody, right? That's exactly what I dislike in this patch - too much assumptions about how people work, neither of which has anything to do with the system itself but only with this particular kludge. SF>>resource id, and it would need to be a ZTS build. Whatever way you look at SF>>it, that's a screwed up configuration. So we would blame the user for our broken code. Do you think it's a good idea. -- 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
