On Thu, June 1, 2006 12:21 am, Frank M. Kromann wrote: >> Fine, but breaking working code while you're trying to understand >> what's > >> happening is far from beneficial to our users. Can't we at least #0 >> it? > > There is no need to break code. The shutdown function was commented > out > for a reason (crash) when that's fixed we can enable that code again.
I believe this entire part of this thread stems from a suggestion to un-comment that on DEVELOPMENT MACHINES. The OP did only implied the DEVELOPMENT MACHINE, however. It was only a suggestion that debugging it in CGI would be easier than in CLI, or at least more common for development users to hit it enough to FIX it, instead of letting it fester. It's possible the OP meant to CVS commit such a change, but I would hope not... -- Like Music? http://l-i-e.com/artists.htm -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
