I once pushed this hard for namespaces. Then, after years of it being shot down, they did it.
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.
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
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.--Kris
On Wed, Feb 29, 2012 at 2:35 PM, Arvids Godjuks arvids.godjuks@gmail.comwrote:
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