On Jan 3, 2008 8:23 PM, Derick Rethans <[EMAIL PROTECTED]> wrote: > On Thu, 3 Jan 2008, Stanislav Malyshev wrote: > > > > When the type hint says I want an integer, then only integer should be > > > accepted; no casting should be done. It may give predictable results > > > > Why people that want Java just don't use Java I wonder? PHP never was a > > strict > > static typed language. > > Broken record perhaps? I am getting a bit tired of this "just use Java > argument", it's perhaps even a bit arrogant.
It is arrogant. For what I see the strictness is making its way in php simply like OO made it. First we resist (we all remember how hard it was to introduce OO API to some extensions "why bloat it with OO?"). In doubts, we only need to look at all the OO strictness we added in the past versions. Please not that I use "we" for all php internals developers, as a group (even if we all have different opinions, we reflect only one in our releases). > From what I read there is > plenty of people that want type hints for static types - there's a few > patches out there, it doesn't slow down the general case. So why should > we *not* add it? (And yes, I changed my mind) Mines was always in favor of strictness for all types. As it is not necessary to create clean code, it is a really nice addition to bring PHP to yet another good level. Without talking about reducing the WTF in some cases, especially when you have to work in teams with developers not aware of PHP's "weirdness" (please don't tell me to ask them to RTFM, that's off base). Cheers, -- Pierre http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
