Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58197
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.49 as permitted sender)
Received-SPF: pass (google.com: domain of tyra3l@gmail.com designates 10.224.212.134 as permitted sender) client-ip=10.224.212.134;
MIME-Version: 1.0
In-Reply-To: <CAKOpQSx_tJfrRx4uRDfcP94bN1qYw=WOktCKf3Xt-AizN=Lk0A@mail.gmail.com>
References: <CAG=uTXEfTBqX7n0_zfGjB_txQFKtZXF4MOo6RHHPSRPerGeKZA@mail.gmail.com>
	<CAKOpQSwP_VXazO1WgQgOWiKTmgiwzorg2=ii+Mdz58a=TKs6VA@mail.gmail.com>
	<CAGovj_O5UQx9aAaYg302i-kKp13CtBKNLmQ48OLHNvk61rM1sw@mail.gmail.com>
	<1330357150.2159.30.camel@guybrush>
	<CAGovj_MUt60EJfG8a7r-cqrC2PKsi8mqh6v_iyNoRDq8q-jh2Q@mail.gmail.com>
	<CAH-PCH6Bre5yzc6r3zxEj3=zZY0PHDOCVQ0s=f8JBDSPnK+5Fw@mail.gmail.com>
	<CAAyV7nFmfhb97CGAK1ZAkp9qb3oCPxbUDnS-Z-v3cP2APcYs=g@mail.gmail.com>
	<CAKOpQSwTGMcuGs5fDvA0kF7QJamooU7hnqtDFMaCh80amt7kcQ@mail.gmail.com>
	<CAKOpQSx_tJfrRx4uRDfcP94bN1qYw=WOktCKf3Xt-AizN=Lk0A@mail.gmail.com>
Date: Mon, 27 Feb 2012 22:24:54 +0100
Message-ID: <CAH-PCH6r8naSDytcHM1kWWps_6rQrAtUbCHsk+B07kDTFygs7A@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
Cc: Anthony Ferrara <ircmaxell@gmail.com>, Michael Morris <dmgx.michael@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf300fac4dcf7dd804b9f8bd29
Subject: Re: [PHP-DEV] Scalar type hinting
From: tyra3l@gmail.com (Ferenc Kovacs)

--20cf300fac4dcf7dd804b9f8bd29
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 27, 2012 at 8:15 PM, Kris Craig <kris.craig@gmail.com> wrote:

> Now, to rewind a bit past the latest chunk of "I hate this idea" posts...=
.
>
> I'd like to suggest a new term:  "strong".
>

I think it would be better if we could not introduce terms for new
definition if that term is already used in the vocabulary for type systems:
http://en.wikipedia.org/wiki/Strong_typing


>
> This term would be similar to "weak", except with a few key differences:
>
>    - Weak would behave very much like Arvids suggested in his earlier
>    post; i.e. if the variable is an integer but you pass a string (like "=
aaa")
>    to it, a warning would be thrown and PHP would attempt to convert it (=
i.e.
>    it would become 1).
>
> why would "aaa" turn to 1? it would be 0 by the php type juggling rules.


>
>    - Strong, on the other hand, would throw a fatal error if you
>    attempted to pass an incompatible value to an array.  Or, to put it an=
other
>    way, if the "converted" value does not match the original value.  For
>    example, if we're assigning "aaa" to an integer, that would convert to=
 1;
>    and, since "1" !=3D "aaa", a fatal error would be thrown.  On the othe=
r hand,
>    if you were to pass the string "1" to that integer variable, it would
>    convert to 1; and, since "1" =3D=3D 1, there wouldn't be a problem.
>
> same error here, it seems that it isn't the typo. putting that aside: so
you say that the type checking would behave the same was as does currently
the =3D=3D and =3D=3D=3D operator.

>
>    - In both instances, if the converted value matches the original (i.e.
>    "1" =3D=3D 1), no warning error would be displayed.  Should it perhaps=
 display
>    a notice though?  Or no error at all?  I can think of reasonable argum=
ents
>    on both sides of that question.
>
>
I remember seeing that suggestion before, I think that it was proposed more
than once, see
http://marc.info/?l=3Dphp-internals&m=3D128159992610321&w=3D3
did you read that thread?

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--20cf300fac4dcf7dd804b9f8bd29--