Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93226
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.45 as permitted sender)
Sender: Michael Wallner <mike.php.net@gmail.com>
To: internals@lists.php.net
References: <CAFMT4NqTm6z-QYt2SOUMWtcDv+dzFtBEMcKRfcXE-DP0SpzkOQ@mail.gmail.com>
 <CAFMT4NoZtTDZmift7RVn9omvfHJFF1c0pnN8N0rBR=sh42q+Nw@mail.gmail.com>
 <573232DB.8030209@lsces.co.uk>
 <CAFMT4NrtkD97tKsfawxUyVR1smSsbKCj-i=SWgRiemp_PWtzkg@mail.gmail.com>
 <573308EC.70502@lsces.co.uk>
Message-ID: <57330C7D.5070901@php.net>
Date: Wed, 11 May 2016 12:42:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <573308EC.70502@lsces.co.uk>
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="3tSabhuVsDkhjVW4fhiw08rB3ESSemHkS"
Subject: Re: [PHP-DEV] Re: [RFC][VOTE] Nullable Types
From: mike@php.net (Michael Wallner)

--3tSabhuVsDkhjVW4fhiw08rB3ESSemHkS
Content-Type: multipart/mixed; boundary="eCPWp0r3XgloCFPTqGbAqTwfFkD001HWq"
From: Michael Wallner <mike@php.net>
To: internals@lists.php.net
Message-ID: <57330C7D.5070901@php.net>
Subject: Re: [PHP-DEV] Re: [RFC][VOTE] Nullable Types
References: <CAFMT4NqTm6z-QYt2SOUMWtcDv+dzFtBEMcKRfcXE-DP0SpzkOQ@mail.gmail.com>
 <CAFMT4NoZtTDZmift7RVn9omvfHJFF1c0pnN8N0rBR=sh42q+Nw@mail.gmail.com>
 <573232DB.8030209@lsces.co.uk>
 <CAFMT4NrtkD97tKsfawxUyVR1smSsbKCj-i=SWgRiemp_PWtzkg@mail.gmail.com>
 <573308EC.70502@lsces.co.uk>
In-Reply-To: <573308EC.70502@lsces.co.uk>

--eCPWp0r3XgloCFPTqGbAqTwfFkD001HWq
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 11/05/16 12:26, Lester Caine wrote:
> On 10/05/16 21:26, Levi Morrison wrote:
>> It can affect the results.
>>
>>     function foo(?Foo $param) {}
>>
>> If any code out there is calling foo with null then that code will now=

>> break if you remove the question mark.
>=20
> Cart before Horse comes to mind ...
>=20
> If the function is going to fail if you pass in a null ... you check fo=
r

Why do you assume it'll fail?

> the null before calling it. OK the '?' is a flag that you need to do
> that, but you really need proper documentation as to just what Foo
> expects. If I've handled the null case situation, the ? is redundant?
>=20
> I'm still failing to see an overall picture of what people are trying t=
o
> achieve. Adding errors means that those errors need to be handled. If
> the function gets a 'null' then there is a reason, and either the
> function should not have been called ... workflow failed ... or the
> function should simply handle the 'null' case. If the '?' throws an
> error the workflow is broken after the event where a user code warning
> would be more helpful.
>=20

	function foo(?Foo $param)

is equivalent to

	function foo(Foo $param =3D null)

except the former does not provide a default, i.e. it requires an
argument being passed to a call to foo().

--=20
Regards,
Mike


--eCPWp0r3XgloCFPTqGbAqTwfFkD001HWq--

--3tSabhuVsDkhjVW4fhiw08rB3ESSemHkS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJXMwx9AAoJEEgOPhSwpMfHwVEIAIo4bvkwbyw3YGUoLJ0JXUSS
9LkI/ebE4jdjZUkV8wWbX5VXd4NZ37h7YKDkK5jANSqvUqoiYJctYTreHDH5wbNd
k+inMIHmyZ/cAoVKYMcRY7PCjZTPgL+riBr9jlF8d9DGDwU7gIAVitd2EoBLStws
nJflC7p4curLC4+LPZq/bVWFXjWJ5emChZsD4JMem51lEPZ1JcJT/9ZzFa6Ytiwj
+UQZay5X4V3NCqNj6nmkclDhLBzUl7RvmQqErvSmQZ0S4fzwMBsJV5e1D8qOdGWE
+CL1PiC45Hz9kmBdoPpMSfFyiHJ472lMbdUDeXr1WoH90aCUKDV2bKTnGkUM1k0=
=7zd6
-----END PGP SIGNATURE-----

--3tSabhuVsDkhjVW4fhiw08rB3ESSemHkS--