Date: 09/30/01
- Next message: derick <email protected>: "Re: [PHP-DEV] Bug #13478 Updated: array_merge changes keys"
- Previous message: derick <email protected>: "Re: [PHP-DEV] why does exit() print its argument?"
- In reply to: Rasmus Lerdorf: "Re: [PHP-DEV] why does exit() print its argument?"
- Next in thread: derick <email protected>: "Re: [PHP-DEV] why does exit() print its argument?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: derick <email protected>: "Re: [PHP-DEV] Bug #13478 Updated: array_merge changes keys"
- Previous message: derick <email protected>: "Re: [PHP-DEV] why does exit() print its argument?"
- In reply to: Rasmus Lerdorf: "Re: [PHP-DEV] why does exit() print its argument?"
- Next in thread: derick <email protected>: "Re: [PHP-DEV] why does exit() print its argument?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

