Andi Gutmans wrote:
> At 07:58 AM 2/7/2002 +0100, Stig S. Bakken wrote:
>
>> After careful consideration on the CS issue I must say I agree with John
>> here. The _only_ case where I feel CS is a problem, is when dealing
>> with other environments. But the price for changing this today is
>> simply too high. It should have been done in PHP 3.0. We have other BC
>> issues to soak our brains in.
Why not in PHP5? PHP5 breaks BC badly with new name space
support, anyway. Obviously, main concern for PHP5 is not
compatibility, not like PHP4. Right?
>>
>> HOWEVER, I would like to suggest one compromise: storing class names
>> (and maybe function names) exactly as they were spelled in the
>> definition, and have get_class() etc. return that version instead of the
>> lowercased one. This would at least make us able to expose interfaces
>> with the intended case.
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.
<?php
class Foo() {
var v = 'abc';
}
$obj = new FOO;
if (get_class($obj) === "foo") {
// do something useful
}
?>
BTW, this is one the case that automatic case conversion
for case sensitive name is difficult...
>>
>> -1 from me on case sensitivity in ZE2, +1 on storing "pretty names"
>
>
> I agree and I'll try and check if pretty names can be handled.
>
> Andi
>
If we don't come to conclusion, even if there is serious problem
with ini switch, I vote +1 for case sensitivity ini switch for
the sake of PHP future. We may clean up the ini entry with PHP6.
--
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
