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. >> >> 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. >> >> -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 >
One more comment :) I guess the original reason why PHP has case insensitive class/function names is consistency with HTML standard. If so, XHTML _is_ case sensitive, we should go for case sensitive names. If PHP aims to be most a productive web scripting language, we should go for case sensitive names for other web related technology, also. Right? -- 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
