php-developer-list | 2001122
Date: 12/21/01
- Next message: jerenkrantz <email protected>: "[PHP-DEV] Bug #14637: Apache 2.0 filter and PHP 4 crash"
- Previous message: derick <email protected>: "[PHP-DEV] Bug #13447 Updated: Security not blocking "unlink" delete functions"
- Next in thread: Brian Moon: "Re: [PHP-DEV] exit()"
- Reply: Brian Moon: "Re: [PHP-DEV] exit()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guys,
I just read the whole thread about exit() now. Boy you guys write a lot :)
Unlike Zeev I think that overloading exit() is the best solution we have
right now.
Have exit(integer) exit with an exit status and exit("string") print the
error. I also very much liked the proposal of exit(string, integer) where
it would behave correctly with exit("foo"), exit(5) and exit("foo", 5).
I think BC is an issue and I wouldn't want to break stuff during a 4.x
release. It's not as if people can't survive with the way it is today
(people have survived for a long time). If it doesn't change tomorrow
morning it's not like PHP will fall apart.
How about changing this for PHP 5?
Andi
P.S. - Just a small suggestion. When people write essays in E-mails please
see if they can't be shortened whilst still saying all you wanted to say.
It sometimes takes a looooooooong time to read all of these threads :)
-- 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: jerenkrantz <email protected>: "[PHP-DEV] Bug #14637: Apache 2.0 filter and PHP 4 crash"
- Previous message: derick <email protected>: "[PHP-DEV] Bug #13447 Updated: Security not blocking "unlink" delete functions"
- Next in thread: Brian Moon: "Re: [PHP-DEV] exit()"
- Reply: Brian Moon: "Re: [PHP-DEV] exit()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

