Re: Breaking backwards compatibility - good or bad?
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.lang.php archive

Re: Breaking backwards compatibility - good or bad?

From: Wayne <not@here.com>
Date: Tue Jan 03 2006 - 07:42:19 CET

On Sat, 31 Dec 2005 18:20:11 +0000, Colin Fine
<news@kindness.demon.co.uk> wrote:

>Wayne wrote:
>> On Sat, 24 Dec 2005 11:10:33 +0000, Colin Fine
>> <news@kindness.demon.co.uk> wrote:
>>
>>
>>>PHP5 marked a step forward over PHP4, but Tony has changed my mind.
>>>The one place where it has improved things (that I can now say
>>>class MyClass
>>>...
>>>if get_class($var, 'MyClass') ...
>>>and have it work)
>>>is not enough to justify the change.
>>
>>
>> The reason for the change was for __AutoLoad(). Since most file
>> systems where PHP runs is case-sensitive you need to get the proper
>> case of the class to map it to a file name to load.
>>
>> That's the reason for that change.
>>
>
>So what happens if you use it on an OS with case-insensitive filenames?

It still works fine. Just don't have two files (two classes) with the
same name matching the same case. I run my PHP5 project on Windows
and Unix -- works perfectly.
Received on Tue Jan 17 16:51:36 2006