Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85204
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAMyk_Aa+V98=mBveH2trbC32NnNy4cFH7hfO53c-hEb4RY93XA@mail.gmail.com>
References: <CAAyV7nEtdFSdPMieK0EvdO+moCqDw7KH59=Lr3+pA10rn=isoQ@mail.gmail.com>
	<CAB6YZuzrokpubXKKOzeM5tH=n2K6WPfX+YDwyKb4tByg33G7zw@mail.gmail.com>
	<CACwt+JdBDN95uN8csq5UaELozj3P4wbswhaYxvZ2hqh5JjALLw@mail.gmail.com>
	<CAB6YZuzkxWWq7ZA29TZVDsX7zBaEMvUGU7MC0gyuZHyZMNpqMQ@mail.gmail.com>
	<CALuY8tg_-AS9KYV-tKEBnrgbotszh_rZkfGg0dBAjLATpWRoSg@mail.gmail.com>
	<CAB6YZuy9dVaNvKiai8UExigQTt8tjC=FwK_XeOqmofpATgfDPQ@mail.gmail.com>
	<CALuY8tgw1rC+9jw1szQAAk0t7GjByPaM_JSVwzF-fqr0nUXV0w@mail.gmail.com>
	<CAB6YZuxvWX7u-iyBVOArfVOqbcVLiVoPCGjFRtDW9OkVKubbqw@mail.gmail.com>
	<CAGAGxbaFJ5anL6vr8RYn7=teFsqMSQJYs=pMXACeiaxzzj4vRw@mail.gmail.com>
	<CAMyk_AbSDDq7udufxoWSR8Ajsp=-m_e+fUcPQzh+v7ow0=R2mg@mail.gmail.com>
	<CAGAGxbat+qEabHK_WJWHfqfXM65BQmhBnHj-mVK03ri3wtJp9Q@mail.gmail.com>
	<CAMyk_Aa+V98=mBveH2trbC32NnNy4cFH7hfO53c-hEb4RY93XA@mail.gmail.com>
Date: Wed, 18 Mar 2015 23:46:27 +0100
Message-ID: <CAOjCV8wrxqsOKkQmkWDi=TxL232_E=O+WJeJVQcmDW6upeR_=Q@mail.gmail.com>
To: Lazare Inepologlou <linepogl@gmail.com>
Cc: Chris Wright <cw@daverandom.com>, =?UTF-8?Q?Pavel_Kou=C5=99il?= <pajousek@gmail.com>, 
	Nikita Nefedov <inefedor@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC][Accepted] Scalar Type Declarations V0.5
From: sbj.ml.read@gmail.com ("Sebastian B.-Hagensen")

Hi,

2015-03-18 20:42 GMT+01:00 Lazare Inepologlou <linepogl@gmail.com>:
> However, it seems that the second form is possible to fail, and that
> depends on the mode (strict or not) of the library that contains the
> function a. It does not depend on the mode that I have chosen to work with.
> The two closures will not work in the same way and that's a kind of a WTF
> moment.

If the library documents that it is passing an int or an intable value
in non-strict to the callback and it does not do so it has a bug. If
the library does not declare a type and you hint an int and it passes
something else, you created a bug.  However, to work in a real code
base some discipline and clean documentation from the library author
is required. But I agree that this is currently fragile. Having a way
to hint a callables signature may not solve the issue , but make it
easier to catch and shift most, if not all, responsibility to the
library author.