At 07:24 30-09-01, Markus Fischer wrote: >Zeev, > >You are right that there is no immidiate reason for changing >exit() right now to behave as expected. > >However, I think most have to admit that its a bad story[tm] that >exit() evolved to it what it is right now. As you see many people >expect exit() to behave like its C counterpart; and, there is >nothing wrong assuming so.
PHP is a language where the C equivalent of exit() makes very little sense. The way I see it is that there's nothing wrong with the way it is, and the minor annoyance with the way it is definitely doesn't warrant a BC breaking change. I, for one, think that the way exit() is is useful, and I'm sure there are others. We've discussed several times whether PHP should be copying other languages (namely C) or not, and in recent years/months, the common concensus is 'no' - it's a language on its own right, with unique semantics, especially when there's a core function that's very unique to shell programming, that makes very little sense in a non-shell context, which accounts for most of PHP's installations. I've been in favour of breaking BC with much more fundamental issues (like register_globals) when there was a good reason for it. There simply isn't any reason for exit() not to be the way it is, and definitely, there's no overwhelming reason to change it from the way it is. Zeev -- 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]
