Marko Karppinen wrote:
> Yasuo:
> 
>>Hmm. I vote -1 for this.
>>It just does not make sense to store original(case sensitive)
>>names while langage ignores case. It's also confusing, lead
>>to case sensitivity BC problem anyway just like with case
>>sensitive function/names.
>>
> 
> Case preservation makes very much sense in a case-insensitive environment.
> Just look at file system implementations from Apple and Microsoft, where,
> believe it or not, a lot of thought has gone into this issue.
> 
> I had a private chat with Jason Greene about this, and I came out with the
> understanding that the .NET/SOAP interop issues mentioned here earlier by
> Markus and Jason are actually issues with PHP not preserving case rather
> than with PHP not being fully case-sensitive.

It will be confusing PHP preserve case for other while
internally case insensitve...

Therefore, -1 for this :)

> 
> And since Andi promised to take a shot at making case preservation happen,
> it seems like we are on our way to better interoperability without too much
> BC hassles.

If get_class() or like returns names with case preserved,
it breaks BC. I expect additional parameter for all of
these functions if it really implemented.

I hope not, since it's a additional memory and performance loss...
-- 
Yasuo Ohgaki


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


-- 
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to