Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58366
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
Received-SPF: pass (google.com: domain of shadda@gmail.com designates 10.50.236.73 as permitted sender) client-ip=10.50.236.73;
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <CAKOpQSxSZ-nhM_Z8nn6M3oA_xwWX2HtTj9yy5Nw1JN8q9zZtPw@mail.gmail.com>
Date: Wed, 29 Feb 2012 16:46:54 -0600
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <43409D28-75AC-4E9C-A0EA-66FC1DB9FAE7@gmail.com>
JEwG=VKow@mail.gmail.com> <887FE7CFF6F8DE4BB3A9535F53AFD06AC3152C6C@il-ex2.zend.net> <CAKOpQSy14SKeVHATHp65HyGnf1wpM=2Gie9K0BSXgvdi4REzXw@mail.gmail.com> <887FE7CFF6F8DE4BB3A9535F53AFD06AC3152F5D@il-ex2.zend.net> <CAKOpQSxqFniCYu-86HJ2-no-z8C+fpj_h0mDh6db5K4QHxpiVg@mail.gmail.com> <CAL0xaBGM6xyOKcV3Z6FijEn6WDnFX1jJCbM=qLvrGmtX1_1J7Q@mail.gmail.com> <CAKOpQSyNmhHyXGcvW975J_0+UH+f_jx+O8E-w8BHPT3wAHZZMg@mail.gmail.com> <CAL0xaBHkqEpNG=MtkL=G=HLtWstx-BeVoLHRpen7aENHNR6scg@mail.gmail.com> <CAKOpQSxSZ-nhM_Z8nn6M3oA_xwWX2HtTj9yy5Nw1JN8q9zZtPw@mail.gmail.com>
To: Kris Craig <kris.craig@gmail.com>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [PHP-DEV] Scalar type hinting
From: shadda@gmail.com (Matt Wilson)

I once pushed this hard for namespaces. Then, after years of it being =
shot down, they did it.=20

And now I'm sad. It didn't occur to me until after it had been =
implemented how bad an idea it was for php. I think this is one of those =
times.

Type hinting is wonderful, but i'm not sure you could really make it fit =
in php without bastardizing the concept.=20

The last time I looked at this discussion, I saw something about =
call-time silent type conversion (essentially foo((int) $bar)) and if =
that's not bastardizing a concept...

I think the community has spoken. And when the core devs put their foot =
down, I think it's best to listen. If it's so important to you, then by =
all means, fork. Or simply write a patch. Put it to a vote. But this is =
beating a very dead horse.

-M

On Feb 29, 2012, at 4:36 PM, Kris Craig wrote:

> I agree.  I'm against strict type hinting as well.  Of course, nobody =
here
> is suggesting that we should go with strict typing, so it's a moot =
question
> anyway.
>=20
> --Kris
>=20
>=20
> On Wed, Feb 29, 2012 at 2:35 PM, Arvids Godjuks =
<arvids.godjuks@gmail.com>wrote:
>=20
>> Please.read my emails carefuly. What i said is last time the work has =
been
>> done, and two different patches have been developed and iterated. But
>> dificulties in implementation and strong resistance from the devs and
>> comunity got it killed. I actually had a post on our biggest russian
>> speaking IT resource and results shown that majority of comunity was
>> against strict type hinting - it does not fit PHP philosophy. Simple =
as
>> that.
>> Thats all, if you cant unders
>>=20