Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:84027
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain damz.org designates 74.125.82.49 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4ED7146272E04A47B986ED49E771E347D3111ACD71@Ikarus.ameusgmbh.intern>
References: <d238d736f8fcde9e649cb38c9b05fcc1@mail.gmail.com>
	<CALWK-fik9mKAd=GymAocpq0rJOaGhPnvfD+PDA-5BKwkh4wHGA@mail.gmail.com>
	<4ED7146272E04A47B986ED49E771E347D3111ACD71@Ikarus.ameusgmbh.intern>
Date: Fri, 27 Feb 2015 17:46:31 +0100
Message-ID: <CALWK-fh6yiXmH_wY-5Hu0Ui68HhCo76i2ZxjETFACmFeySvdCg@mail.gmail.com>
To: Christian Stoller <stoller@leonex.de>
Cc: Zeev Suraski <zeev@zend.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b5d283452a4510510149c80
Subject: Re: [PHP-DEV] Coercive STH - some real world tests and updated RFC
From: damz@damz.org (Damien Tournoud)

--047d7b5d283452a4510510149c80
Content-Type: text/plain; charset=UTF-8

Hi Christian,

On Fri, Feb 27, 2015 at 5:15 PM, Christian Stoller <stoller@leonex.de>
wrote:

> In this case FALSE is an expected result and it is intended. And as
> I said other languages are going the same way.
>

Other languages are also doing something saner. It's not really an argument
either way.

Just because it makes more sense for you, it does not imply that
> it makes more sense for everybody. In my opinion it makes sense to
> return an "error code" if a function is called with invalid
> arguments.
>

You probably haven't read the examples that I pasted. If you think that it
makes sense to return an error code if the function is called with invalid
arguments, it should be done consistently. The current behavior is just an
absurdly inconsistent, it is really hard to find an argument in favor of
it, other than the argument in favor of backward compatibility.

Damien

--047d7b5d283452a4510510149c80--