Re: [PHP-DEV] why does exit() print its argument?
Web scripting language, I think that the chances of people expecting this I use it as a system scripting language and vote +1 for numeric arguments to work the expected way. I want to use it as a system programming language. But fork() is missing :) Anyway this shows we use php for many differenet applications and purposes. That's not the reason to break BC. Lenar -- 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]
Re: [PHP-DEV] why does exit() print its argument?
On Mon, 1 Oct 2001, Lenar wrote: I want to use it as a system programming language. But fork() is missing :) Fork is not missing, pctnl_fork is the name iirc. Derick -- 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]
Re: [PHP-DEV] why does exit() print its argument?
[Zeev Suraski [EMAIL PROTECTED]] The WTF factor is generally higher with magical stuff like that. It's not too far fetched to realize a situation where a 'WTF?' will be flown into the air, just because the error message happened to be 1, or 20... shell_exit() is not a very good name. That's why I haven't failed to mention, every time I mentioned it, that a better name would be better. We can have exit_with_status(), silent_exit(), etc. exit_with_status() is good. - Stig -- Stig Sæther Bakken [EMAIL PROTECTED] Fast Search Transfer ASA, Trondheim, Norway -- 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]
Re: [PHP-DEV] why does exit() print its argument?
On Fri, 28 Sep 2001, Rasmus Lerdorf wrote:
How about if we overload it a bit. I think anybody who does exit(1) is
expecting 1 to be set as the return status whereas someone who does
exit('something bad happened') is expecting the string to be shown a-la
die(). So let's just check the arg and do the appropriate thing. I would
be very surprised if that broke anything.
Exactly what I was thinking of, and just wrote...
Derick
--
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]
Re: [PHP-DEV] why does exit() print its argument?
Markus Fischer wrote: Usualy I am very much against breaking backwards compatibility, but in this case I think it's the best thing to do... Because: - It's already documented that way - It's the 'expected' behaviour (from other languages, and from the docs) As Rasmus said: It would be surprising if this broke a lot of (or even any) code. +1 Hey, my second vote O_o -1 for PHP 4.0.x +1 for PHP 4.1 or greater. -- 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]
