Re: Question: Should exit() print out the integer exit-status?

From: Date: Wed, 19 Dec 2001 16:29:26 +0000
Subject: Re: Question: Should exit() print out the integer exit-status?
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-74429@lists.php.net to get a copy of this message

1. Because this is how things are done in PHP always..since PHP 3?
2. PHP != C/C++/Java/Perl/Python
3. Zeev says so
4. BC
.
.
.

It's totally useless to make any sense into the language as long
as functions are 'fixed' by adding new functions, new (optional)
arguments are added..etc. I do agree that BC is important.
But is it really wise in a long run?

So far only Zeev has found one script which would break. And
which also can be fixed very easily. This really doesn't prove
his point that fixing the behaviour to be correct would
'break thousands of scripts' and make people angry.

(It still is not clear why someone wants to _see_ the exit status
printed out when not explicitly said so..ie. when it's an integer?)

--Jani


On Wed, 19 Dec 2001, Jason Greene wrote:

>Zeev,
>
>Why don't we follow C/C++/Java/Perl/Python, and almost every other
>language on this one, and make exit behave like exit should.
>
>-Jason
>
>----- Original Message -----
>From: "Zeev Suraski" <zeev@zend.com>
>To: "Lars Torben Wilson" <torben@php.net>
>Cc: <derick@php.net>; "Vlad Krupin" <vlad@php.net>; "Jani
>Taskinen" <sniper@iki.fi>; "PHP Developers Mailing List"
><php-dev@lists.php.net>
>Sent: Wednesday, December 19, 2001 6:59 AM
>Subject: Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?
>
>
>> 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
>>
>





Thread (53 messages)

« previous php.dev (#74429) next »