Fixing a bug by adding new function that behaves correctly is really not the way to go. Could you please give me nice example what kind of scripts break if the integer is not printed out?
--Jani On Wed, 19 Dec 2001, Zeev Suraski wrote: >exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something >should fit :) > > >At 14:49 19/12/2001, Lars Torben Wilson wrote: >>Zeev Suraski writes: >> > At 14:04 19/12/2001, [EMAIL PROTECTED] wrote: >> > >Two ways to fix it then, either update the manual, or fix exit(). I go for >> > >the last one then. Ppl who relied on the undocumented feature then, did >> > >simply the wrong thing. >> > >> > Only the documentation was wrong to begin with! A documentation bug >> should >> > not become a feature, especially when it never worked that way, so anybody >> > who actually used this function saw that it was behaving differently. >> > >> > Zeev >> >>Well, from another point of view, both were wrong. :) The manual >>documented behaviour which didn't exist, so it was wrong. In another >>sense, the code behaved in a fashion which had a very high WTF factor, >>so it couild be called 'wrong' too. >> >>An easy way to set and check the exit status of a PHP script would >>make a lot of life a hell of a lot easier. >> >> >>-- >> Torben Wilson <[EMAIL PROTECTED]> >> http://www.thebuttlesschaps.com >> http://www.hybrid17.com >> http://www.inflatableeye.com >> +1.604.709.0506 > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
