On Wed, Jan 29, 2014 at 11:05 AM, Andrey Hristov <[email protected]> wrote:
>
> not the language is silly, the developers are. Why C doesn't forbid out of
> range accesses on arrays. Is the language silly?
>
>
Yes, I do think PHP is being silly. Again, treating "T" and "t" like
they're the same thing? They're not. One is an upper case T, one is a
lowercase t. They look different. They are different ascii and unicode
character codes. Languages that conform to this: Python, Ruby, C and Java.
Why does PHP feel the need to try to translate this developer typo?
Is this a beneficial "feature" of PHP? I don't think so. As I've harped on,
it definitely creates issues with autoloading across different platforms
when namespace or class names are cased improperly.
It's a big backwards comparability break, but one that's very easily fixed
with a third party tool that analyzes the code base for violations during
an upgrade phase.
I'd love to see it fixed in the next major PHP release. It is silly. I'm
sticking by that.