someone created it for debugging and forgot to remove and the search engine stumbled across it. It happens.
OK, I was overreaching. But main point stays - problems of configuration are rarely solvable by automatic means, rather by education and choosing better defaults. If you run site in debug configuration, there's little we can do - debug configuration is _supposed_ to reveal information. However, there's a bunch we could do about errors of omission - e.g. people just not doing stuff which they should do because they forget or didn't check their code thorough enough. That is as if we had switch that says "production mode" which could filter out all info that could be potentially dangerous, etc. - it would help such phpinfo() people, if we solve chicken and egg problem of having them to actually turn the switch on :) BTW, may be an idea to think about too :)
I am saying that you should not try to outsmart the developer because you assume you know best.
Well, if you don't take me personally - I certainly don't - but collective judgment of the PHP group - that to some measure that is the way, we try to guess what developers need and steer the language accordingly. There's no way of not doing it - you always make choices to do or not to do certain feature and how to do it.
-- 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
