In past years such switches where deprecated and removed (in 5.3 most of
them, in 5.4 finally all that stuff is gone for good). So any solution,
involving a switch that modifies how code is executed will hit a wall of
resistance. It's the lesson that was learned the hard way.

So it may be the case to make PHP case-sensetive. There will be code
broken, probably a lot. But that can be fixed, and I personally always
write with respect to char case, so that will be no problem for me.

20 апреля 2012 г. 13:20 пользователь C.Koy <can5...@gmail.com> написал:

> Hi,
>
> This post is about bug #18556 
> (https://bugs.php.net/bug.php?**id=18556<https://bugs.php.net/bug.php?id=18556>)
> which is a decade old.
>
> As the recent comments on that page indicate, there's not a deterministic
> way to resolve this issue, apart from eliminating tolower() calls for
> function/class names during lookup. Hence totally case-sensitive PHP.
>
> Before opposing with "No, this will break a lot of existing code!", note
> that I'm not suggesting a static permanent change in the engine; rather a
> runtime option that will need to be enabled (cli option, INI setting),
> without which PHP will work as before.
>
> Since I'm not well versed in the workings of Zend engine, I solicit the
> wisdom/experience of people in this list: Is this doable in a practical
> way, without making grand changes in Zend?
>
> best regards,
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Reply via email to