Date: 09/28/01
- Next message: Zeev Suraski: "Re: [PHP-DEV] why does exit() print its argument?"
- Previous message: mfischer <email protected>: "[PHP-DEV] Bug #13489 Updated: Project Due now and having PHP has encountered an Access Violation at 01A6649C"
- Next in thread: Steve Meyers: "[PHP-DEV] Re: exit() / die()"
- Reply: Steve Meyers: "[PHP-DEV] Re: exit() / die()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Guys,
Changing these is quite out of the question - they've been a core part of
the language since 1997 (at least), and have lots of lines of code that
rely on them. Moreover, there's no clear-cut reason to change it,
especially considering it only makes sense when used in command-line mode,
whereas the current behavior is useful in all SAPIs (in order to introduce
such a compatibility-breaking change, we need a *good* reason).
My suggestion is:
(a) Tracing when exit() started changing exit status. If it was recent
enough, revert.
(b) In the CGI SAPI, introduce a shell_exit() or terminate() (possibly find
a better name), that will exit and set the specified error level.
Zeev
-- 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: Zeev Suraski: "Re: [PHP-DEV] why does exit() print its argument?"
- Previous message: mfischer <email protected>: "[PHP-DEV] Bug #13489 Updated: Project Due now and having PHP has encountered an Access Violation at 01A6649C"
- Next in thread: Steve Meyers: "[PHP-DEV] Re: exit() / die()"
- Reply: Steve Meyers: "[PHP-DEV] Re: exit() / die()"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

