Re: [PHP-DEV] why does exit() print its argument?

2001-10-01 Thread Lenar
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

Re: [PHP-DEV] why does exit() print its argument?

2001-10-01 Thread derick
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,

Re: [PHP-DEV] why does exit() print its argument?

2001-09-30 Thread Stig Sæther Bakken
[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.

Re: [PHP-DEV] why does exit() print its argument?

2001-09-30 Thread Derick Rethans
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

Re: [PHP-DEV] why does exit() print its argument?

2001-09-29 Thread Yasuo Ohgaki
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