I can't remember every single war there has been on php-dev.. :-p Like Jason put it, two GOOD solutions (others are just denying the fact that someone fucked this up when it was implemented):
1. Overload it. 2. Separate die() and exit(). Zeev, are you really using exit() to output integers? What kind of script is it? (just curious) Maybe we should ask on php-general sometimes when we get into discussion whether people rely on something or not? :) Or put up some kind of voting thing on php.net which can be used to find out what the people 'out there' think ? --Jani On Fri, 7 Dec 2001, Markus Fischer wrote: >On Fri, Dec 07, 2001 at 02:33:50AM +0200, Jani Taskinen wrote : >> >> Creating some new function (or language construct :) and not fixing the >> existing one is really stupid idea. >> >> exit(string) -> same behaviour as before >> eixt(int) -> only set exit-status and no echo out anything to stdout. >> >> Thus BC wouldn't be that badly broken.. > > Here are the relevant archive references: > > http://marc.theaimsgroup.com/?t=100170293000002&w=4&r=1 > http://marc.theaimsgroup.com/?l=php-dev&m=99539268507735&w=4 > > - Markus > > -- 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]
