php-developer-list | 2001122
Date: 12/19/01
- Next message: aaron <email protected>: "[PHP-DEV] Bug #14610: configure script looks in the wrong place for httpd.h"
- Previous message: Vlad Krupin: "Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?"
- In reply to: Jason Greene: "Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?"
- Next in thread: Vlad Krupin: "Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
sys_exit()/system_exit() sound nice to me, definitely nicer than all of my
suggestions :)
At 23:13 19/12/2001, Jason Greene wrote:
>Zeev,
>
>I understand argument 1, and that's why I like the idea of overloading
>integer output. I still wonder
>if there is a web page out there that calls exit(integer)
>
>Argument 2 is good, because PHP is focused toward the web, which I
>understand that it should be.
>However, I believe the language syntax and style can make a good general
>purpose scripting language
>as well. Things like this can keep PHP from increasing beyond the 10% cmd
>line usage.
>
>If adding an additional function is all that you will settle for, then I
>would suggest
>we use sys_exit() or system_exit() that way we resemble some of the
>languages out there.
>(Java - System.exit(), Python - Sys.exit())
>
>-Jason
>
>
>----- Original Message -----
>From: "Zeev Suraski" <zeev <email protected>>
>To: "Jason Greene" <jason <email protected>>
>Cc: "Lars Torben Wilson" <torben <email protected>>; <derick <email protected>>; "Vlad Krupin"
><vlad <email protected>>; "Jani Taskinen" <sniper <email protected>>; "PHP
>Developers Mailing List" <php-dev <email protected>>
>Sent: Wednesday, December 19, 2001 2:26 PM
>Subject: Re: [PHP-DEV] Question: Should exit() print out the integer
>exit-status?
>
>
> > Two reasons:
> > (1) It never behaved that way, and we're not in the language design phase,
> > but almost 4.5 years after it got started.
> > (2) The Web being PHP's primary environment where system exit codes have no
> > meaning at all, makes this argument useless in well over 90% (est) of
> the cases
> >
> > If (1) wasn't true, we could consider it, and frankly, chances are it would
> > have ended up behaving like its C counterpart. However, because there's no
> > overwhelming reason to change it other than a few people not liking a
> > longer name for their relatively-rare usage, breaking compatibility makes
> > no sense.
> >
> > Zeev
> >
> > At 17:57 19/12/2001, Jason Greene wrote:
> > >Zeev,
> > >
> > >Why don't we follow C/C++/Java/Perl/Python, and almost every other
> > >language on this one, and make exit behave like exit should.
> > >
> > >-Jason
> > >
> > >----- Original Message -----
> > >From: "Zeev Suraski" <zeev <email protected>>
> > >To: "Lars Torben Wilson" <torben <email protected>>
> > >Cc: <derick <email protected>>; "Vlad Krupin" <vlad <email protected>>; "Jani Taskinen"
> > ><sniper <email protected>>; "PHP Developers Mailing List"
> > ><php-dev <email protected>>
> > >Sent: Wednesday, December 19, 2001 6:59 AM
> > >Subject: Re: [PHP-DEV] Question: Should exit() print out the integer
> > >exit-status?
> > >
> > >
> > > > exit_with_status(), silent_exit(), quiet_exit(), etc. etc. Something
> > > > should fit :)
> > > >
> > > >
> > > > At 14:49 19/12/2001, Lars Torben Wilson wrote:
> > > > >Zeev Suraski writes:
> > > > > > At 14:04 19/12/2001, derick <email protected> wrote:
> > > > > > >Two ways to fix it then, either update the manual, or fix exit().
> > > I go for
> > > > > > >the last one then. Ppl who relied on the undocumented feature
> > > then, did
> > > > > > >simply the wrong thing.
> > > > > >
> > > > > > Only the documentation was wrong to begin with! A
> documentation bug
> > > > > should
> > > > > > not become a feature, especially when it never worked that way, so
> > > anybody
> > > > > > who actually used this function saw that it was behaving
> differently.
> > > > > >
> > > > > > Zeev
> > > > >
> > > > >Well, from another point of view, both were wrong. :) The manual
> > > > >documented behaviour which didn't exist, so it was wrong. In another
> > > > >sense, the code behaved in a fashion which had a very high WTF factor,
> > > > >so it couild be called 'wrong' too.
> > > > >
> > > > >An easy way to set and check the exit status of a PHP script would
> > > > >make a lot of life a hell of a lot easier.
> > > > >
> > > > >
> > > > >--
> > > > > Torben Wilson <torben <email protected>>
> > > > > http://www.thebuttlesschaps.com
> > > > > http://www.hybrid17.com
> > > > > http://www.inflatableeye.com
> > > > > +1.604.709.0506
> > > >
> > > >
> > > > --
> > > > 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>
> > > >
> >
> >
> > --
> > 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>
> >
-- 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: aaron <email protected>: "[PHP-DEV] Bug #14610: configure script looks in the wrong place for httpd.h"
- Previous message: Vlad Krupin: "Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?"
- In reply to: Jason Greene: "Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?"
- Next in thread: Vlad Krupin: "Re: [PHP-DEV] Question: Should exit() print out the integer exit-status?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

