Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58587
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
Received-SPF: pass (google.com: domain of ircmaxell@gmail.com designates 10.229.76.149 as permitted sender) client-ip=10.229.76.149;
MIME-Version: 1.0
In-Reply-To: <CAMyk_AY_zEQtb_emve7j_Hif_SHc-be_0mVd-PS+=V97DoumSg@mail.gmail.com>
References: <CAAyV7nF+yKwrUvyJ7mytQpyLr_HG3M3Pan5cSpLmYjMHFe9X3Q@mail.gmail.com>
	<CAMyk_AY_zEQtb_emve7j_Hif_SHc-be_0mVd-PS+=V97DoumSg@mail.gmail.com>
Date: Sun, 4 Mar 2012 12:17:17 -0500
Message-ID: <CAAyV7nFY=WgvrMwZtA0VFfqNkiQvArnTOFoHT_10fLy=ETap-w@mail.gmail.com>
To: Lazare Inepologlou <linepogl@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=00235429e34c59d28704ba6dfbf3
Subject: Re: [PHP-DEV] [RFC - Discussion] Parameter Type Casting Hints
From: ircmaxell@gmail.com (Anthony Ferrara)

--00235429e34c59d28704ba6dfbf3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Mar 4, 2012 11:47 AM, "Lazare Inepologlou" <linepogl@gmail.com> wrote:
>
>
> Anthony, just a tiny detail in your RCF:
>
>> So (int) $foo =3D null and (int) $foo =3D 1 are both supported, but (int=
)
$foo =3D =931=94 will generate an E_COMPILE_ERROR.
>
>
> If null is going to be cast, (int)null is 0. So I don't think it should
be a valid default value.

Well, there were two reasons that I added null: first, for consistency with
the existing type hints.  Second, and more importantly, to allow checking
if a parameter is specified.  So without null, you couldn't tell the
difference between an explicit 0 and an implicit (not specified) 0.  This
way, you can.  I admit the use cases for that are rather slim, but a good
portion of internal functions behave this way (substr comes to mind)...

I think it is worth discussing further, as your point is indeed valid...

>
> Lazare INEPOLOGLOU
> Ing=E9nieur Logiciel
>
>
> 2012/3/4 Anthony Ferrara <ircmaxell@gmail.com>
>>
>> Hey all,
>>
>> I've drafted an RFC for the Parameter type casting hint proposal that
>> I posted to before.  Attached to the RFC is a patch that's proposed
>> for inclusion in core for functionality (it doesn't include news
>> entries, or documentation, or any of the other steps that would be
>> needed prior to commit).
>>
>> https://wiki.php.net/rfc/parameter_type_casting_hints
>>
>> Please provide feedback here on the implementation and RFC topics.
>>
>> Thanks,
>>
>> Anthony
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>
 On Mar 4, 2012 11:47 AM, "Lazare Inepologlou" <linepogl@gmail.com> wrote:

>
> Anthony, just a tiny detail in your RCF:
>
> So (int) $foo =3D null and (int) $foo =3D 1 are both supported, but (int)=
 $foo
>> =3D =931=94 will generate an E_COMPILE_ERROR.
>>
>
> If null is going to be cast, (int)null is 0. So I don't think it should b=
e
> a valid default value.
>
>
> Lazare INEPOLOGLOU
> Ing=E9nieur Logiciel
>
>
> 2012/3/4 Anthony Ferrara <ircmaxell@gmail.com>
>
>> Hey all,
>>
>> I've drafted an RFC for the Parameter type casting hint proposal that
>> I posted to before.  Attached to the RFC is a patch that's proposed
>> for inclusion in core for functionality (it doesn't include news
>> entries, or documentation, or any of the other steps that would be
>> needed prior to commit).
>>
>> https://wiki.php.net/rfc/parameter_type_casting_hints
>>
>> Please provide feedback here on the implementation and RFC topics.
>>
>> Thanks,
>>
>> Anthony
>>
>> --
>> PHP Internals - PHP Runtime Development Mailing List
>> To unsubscribe, visit: http://www.php.net/unsub.php
>>
>>
>

--00235429e34c59d28704ba6dfbf3--