I think I rather have people bitching about that than bitch about the wrongly set setting. The latter creates bugreports, the first only stupid questions.
I don't consider people bumping into problems upgrading asking questions as being stupid... Most people are not familiar with the ability to put INI settings in the httpd.conf/.htaccess file, at least much fewer than those who are familiar with php.ini...
> Not sure, I'm not even sure whether it should be missing from php.ini or > just have a BIG warning about it, saying it should not be used for shared > hosts...
That's basically inviting them to turn it on :)
I don't think so. I *would* in fact call the people who turn it on without taking this warning into account as stupid.
If shared hosts are our main concern, how about we fail to start if both safe_mode and implicit_clone are enabled, spitting out an error that tells them that they shouldn't be using it in shared environments? Again, just an idea :)
Zeev
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
