> I'm glad I read the list. Doing (a) will break several scripts that my site > depends on.
Ok, I was mistaken in thinking it wouldn't break (a lot of) existing code. > "Zeev Suraski" <[EMAIL PROTECTED]> wrote in message > news:5.1.0.14.2.20010929020430.051aa2a8@localhost... > > 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). You are right. I have been doing some command-line work lately, and I was surprised that exit() didn't do what I expected. But PHP is still (mostly) a web-server language, and there it would make no sense indeed. Changing my vote to -1 on changing and +1 on introducing a new function :) Sander. -- 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]
