Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58158
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 tyra3l@gmail.com designates 10.224.178.136 as permitted sender) client-ip=10.224.178.136;
MIME-Version: 1.0
In-Reply-To: <4F4BB59F.1040708@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>
	<CAKxcST8s37CiArFkEmH6_q4ktz-1u+0AOwFGb=Qv8KrA0pzDdQ@mail.gmail.com>
	<4F4BB59F.1040708@gmail.com>
Date: Mon, 27 Feb 2012 18:07:04 +0100
Message-ID: <CAH-PCH43aCbVPBf08Q02ujSmixR8TM1ba4tF+0PhXB+xveOLjQ@mail.gmail.com>
To: =?UTF-8?B?w4FuZ2VsIEdvbnrDoWxleg==?= <keisial@gmail.com>
Cc: Paul Dragoonis <dragoonis@gmail.com>, =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>, 
	Michael Morris <dmgx.michael@gmail.com>, 
	"internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf303b38adbecbb204b9f523db
Subject: Re: [PHP-DEV] Scalar type hinting
From: tyra3l@gmail.com (Ferenc Kovacs)

--20cf303b38adbecbb204b9f523db
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

>
>
> Now strings. There are two different kinds of strings.
> The first one $age =3D $_POST['age'] is the kind of string that you want =
to
> treat as a number. And that's fine.
>
> But you also have $name =3D $_POST['name'] // 'John Doe' which is wrong
> to treat as a the same as $age.
>
>
php doesn't have the necessary information to tell whether your input
variable is a number, or only looks like a number.
how would you define what is an int? what type would the following input
variables have?
- "1"
- "1.1"
- "1.0"
- ".5"
- "0777"

I think it is better to populate everything as string, and let the
application developer to parse the inputs as he knows what should they
represent.

Btw. there was a discussion about raising a warning (somebody even
suggested creating an E_TYPE level) when data loss occurs on a type
juggling.
I would support that, as people tend to be surprised when they realize the
first time that 123 =3D=3D '123 apples' evaluates to true in php.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--20cf303b38adbecbb204b9f523db--