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: Andy Hassall <andy@andyh.co.uk>
Date: Sat Dec 31 2005 - 19:44:34 CET

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

>> 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?

 Then it picks up the file with the capitalisation matching the class name, but
it's then not portable.

 The main case-insensitive filesystems (FAT32, NTFS) are still case-preserving
anyway, so a file still has a single canonical name capitalised in a specific
way.

-- 
Andy Hassall :: andy@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Received on Tue Jan 3 03:51:06 2006