Re: Question: Should exit() print out the integer exit-status?
| From: | Lars Torben Wilson | Date: | Wed, 19 Dec 2001 13:21:42 +0000 |
| Subject: | Re: Question: Should exit() print out the integer exit-status? | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-74389@lists.php.net to get a copy of this message | ||
Zeev Suraski writes:
> Even if you repeat it may times, it still wouldn't be a bug. When I wrote
> exit() I intended exit() to print out its argument, regardless of its
> type. It's been behaving like this since PHP 3.0.0 alpha 1, because it was
> supposed to behave like that.
> The doc team got it wrong, and misdocumented it.
Only this May. Before that, the docs were correct. Logically, though,
the fact that a member of the doc team replaced the correct docs with
an erroneous description doesn't imply that the function behaved
correctly to start with.
> Scripts who will break are scripts that terminate after printing out an
> error code. I have at least one such script, and I'm pretty sure that more
> exist, especially in automated environments.
>
> Zeev
>
> At 15:08 19/12/2001, Jani Taskinen wrote:
>
> >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, derick@php.net 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 <torben@php.net>
> > >> 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: php-dev-unsubscribe@lists.php.net
> For additional commands, e-mail: php-dev-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
--
Torben Wilson <torben@php.net>
http://www.thebuttlesschaps.com
http://www.hybrid17.com
http://www.inflatableeye.com
+1.604.709.0506