Justtechjobs.com Find a programming school near you






Online Campus Both


php-developer-list | 2001122

Re: [PHP-DEV] Question: Should exit() print out the integer exit-status? From: Yasuo Ohgaki (yasuo_ohgaki <email protected>)
Date: 12/20/01

Zeev Suraski wrote:

> At 15:18 20/12/2001, Yasuo Ohgaki wrote:
>
>> Nobody should complain about BC changes if changes are notified
>> early enough and there is alternative way to do the same thing.
>> IMHO. (This has been done for some features such as track vars ;)
>
>
> That's a very impractical statement in my opinion... Breaking
> compatibility hurts (almost) regardless of when you announce you're
> going to break it. Users would still have to go over their code and fix
> it.

I agree with your opinion also. I think compatibility is one of the most
important aspect of successful software/hardware.
(All of us know how Microsoft and Intel is successful :)

>
> What I *really* fail to understand is the gain we get by modifying
> exit()'s behavior, as opposed to adding a new function or adding a new
> $silent argument. Giving a WFF to several people? Consistency with
> other languages that have nothing to do with the Web environment (which
> is why we got so little complaints about this over *5* years)?

That's too bad.... If I (probably, Markus, Derick and Jani also)
was using PHP at that time, I would strongly object that...

> I see this as very similar to the case sensitivity issue, even though
> this is obviously on a much smaller scale. It's possibly a bad decision
> that was made 5 years ago, but it was made all the same. Since it does
> *not* have far-reaching negative implications, it shouldn't be changed.
>
> Zeev
>

I understand your opinion. I'm not strongly againt to have other

function for retuning exit status. It is just like <?php= ?> to me.
(Better to have one for consistency, but it's not strictly required.
It will not be a reason for many bug reports also :)

BTW, did you notice my proposal for error level and error message
handling? It will break a *LOT* of scripts, but it will give us
a *LOT* of benefits/consistency.

Parhaps, we should discuss how/when/what breaking compatibility(BC)
features should be added/deleted/modified, instead of little spec
like exit()? I have sevral proposals that require BC. I suppose
many people have them, just like you would like to have case
sensitivity for functions :)

PS: I *strongly* agree with you to have case sensitivity for
function names. 

-- 
Yasuo Ohgaki

_________________________________________________________
Do You Yahoo!?
Get your free  <email protected> address at http://mail.yahoo.com

-- 
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>