[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

On Fri, 2002-02-08 at 14:14, Andi Gutmans wrote: > At 01:42 PM 2/8/2002 +0100, Stig S. Bakken wrote: > >On Fri, 2002-02-08 at 13:38, Yasuo Ohgaki wrote: > > > Andi Gutmans wrote: > > > > At 09:20 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: > > > > > > > >> Andi Gutmans wrote: > > > >> > > > Name s

[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

On Fri, 2002-02-08 at 13:38, Yasuo Ohgaki wrote: > Andi Gutmans wrote: > > At 09:20 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: > > > >> Andi Gutmans wrote: > >> > Name space BC problem is "bad", since script may misbehave > without proper error message where to fix. > It's a bad BC pro

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

On Fri, 2002-02-08 at 10:55, Yasuo Ohgaki wrote: > 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

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 01:24 PM 2/9/2002, Thies C. Arntzen wrote: >On Sat, Feb 09, 2002 at 01:41:21AM +0200, Zeev Suraski wrote: > > I think that's a nightmare, WTF-factor wise... Just my 0.02NIS > > how much is that in euro? Not too much. About 0.005 :) Zeev -- PHP Development Mailing List

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

On Sat, Feb 09, 2002 at 01:41:21AM +0200, Zeev Suraski wrote: > I think that's a nightmare, WTF-factor wise... Just my 0.02NIS how much is that in euro? > > Zeev > > At 12:14 AM 2/9/2002, Jason Greene wrote: > >If you are already thinking about storing the case sensitive name for > >the c

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

I think that's a nightmare, WTF-factor wise... Just my 0.02NIS Zeev At 12:14 AM 2/9/2002, Jason Greene wrote: >If you are already thinking about storing the case sensitive name for >the class/function why not follow Rasmus's suggestion for calling the >exact case function first, then look for a

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

On Fri, 2002-02-08 at 06:16, Andi Gutmans wrote: > At 09:06 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: > >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,

[PHP-DEV] RE: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > > >Good idea. E_DEBUG may be a good alternative to php_printf(). Heh. > > Fine tuning errors is probably a good idea. E_PEDANTIC? what i mentioned earlier and still want to see is an E_EXTENSION for errors that are not related to script erro

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

Quoting Yasuo Ohgaki <[EMAIL PROTECTED]>: > 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. It's more confusing, IMHO, to punish peo

RE: [PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

> -Original Message- > From: Andi Gutmans [mailto:[EMAIL PROTECTED]] > Sent: 08 February 2002 13:46 > > At 02:39 PM 2/8/2002 +0100, Stig S. Bakken wrote: > >On Fri, 2002-02-08 at 14:30, Andi Gutmans wrote: > > > At 02:20 PM 2/8/2002 +0100, Stig S. Bakken wrote: > > > >On Fri, 2002-02-08 a

Re: [PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 02:39 PM 2/8/2002 +0100, Stig S. Bakken wrote: >On Fri, 2002-02-08 at 14:30, Andi Gutmans wrote: > > At 02:20 PM 2/8/2002 +0100, Stig S. Bakken wrote: > > >On Fri, 2002-02-08 at 14:14, Andi Gutmans wrote: > > > > At 01:42 PM 2/8/2002 +0100, Stig S. Bakken wrote: > > > > >On Fri, 2002-02-08 at 1

[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 02:20 PM 2/8/2002 +0100, Stig S. Bakken wrote: >On Fri, 2002-02-08 at 14:14, Andi Gutmans wrote: > > At 01:42 PM 2/8/2002 +0100, Stig S. Bakken wrote: > > >On Fri, 2002-02-08 at 13:38, Yasuo Ohgaki wrote: > > > > Andi Gutmans wrote: > > > > > At 09:20 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: > >

[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 01:42 PM 2/8/2002 +0100, Stig S. Bakken wrote: >On Fri, 2002-02-08 at 13:38, Yasuo Ohgaki wrote: > > Andi Gutmans wrote: > > > At 09:20 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: > > > > > >> Andi Gutmans wrote: > > >> > > Name space BC problem is "bad", since script may misbehave > > wit

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

Yasuo Ohgaki wrote: > To use file system as a user, there is no logic required. > (I mean control structures are not needed to use files) > I guess Java/C/C++ is very popular and serious programmers > know at least one of them. Chances are high that new users > get confused by PHP after learnning

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

Hartmut Holzgraefe wrote: > Yasuo Ohgaki wrote: > >> It will be confusing PHP preserve case for other while >> internally case insensitve... > > exactly as confusing as the file systems 90+% of computer users > (Win+MacOS that is) are used to ... > > To use file system as a user, there is no

[PHP-DEV] Re: [Zend Engine 2] Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

Andi Gutmans wrote: > At 09:20 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: > >> Andi Gutmans wrote: >> Name space BC problem is "bad", since script may misbehave without proper error message where to fix. It's a bad BC problem since it's harder to fix/notice. In some cases, it seem

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 01:15 PM 2/8/2002 +0100, Hartmut Holzgraefe wrote: >Yasuo Ohgaki wrote: >>It will be confusing PHP preserve case for other while >>internally case insensitve... >exactly as confusing as the file systems 90+% of computer users >(Win+MacOS that is) are used to ... Amen. Andi -- PHP Developme

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 09:20 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: >Andi Gutmans wrote: >>>Name space BC problem is "bad", since script may misbehave >>>without proper error message where to fix. >>>It's a bad BC problem since it's harder to fix/notice. >>>In some cases, it seems works well while it's not. >> >>The

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

Andi Gutmans wrote: >> Name space BC problem is "bad", since script may misbehave >> without proper error message where to fix. >> It's a bad BC problem since it's harder to fix/notice. >> In some cases, it seems works well while it's not. > > > The question is how often does this breakage actua

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

Yasuo Ohgaki wrote: > It will be confusing PHP preserve case for other while > internally case insensitve... exactly as confusing as the file systems 90+% of computer users (Win+MacOS that is) are used to ... -- Hartmut Holzgraefe [EMAIL PROTECTED] http://www.six.de +49-711-99091-77 Wir ste

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 09:06 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: >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 ca

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

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 preservat

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 07:59 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: >Andi Gutmans wrote: >>At 06:55 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: >> >>>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.

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

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

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

Andi Gutmans wrote: > At 06:55 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: > >> 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,

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

At 06:55 PM 2/8/2002 +0900, Yasuo Ohgaki wrote: >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

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

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

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

Hartmut Holzgraefe wrote: > Yasuo Ohgaki wrote: > 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. >>> > [...] > >> Question is, PHP is go

Re: [PHP-DEV] Re: Case sensitivity: Conclusion(?)

Yasuo Ohgaki wrote: >>> 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. [...] > Question is, PHP is going to be nice to other > web related technol

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

Jim Winstead wrote: > Yasuo Ohgaki <[EMAIL PROTECTED]> wrote: > >>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. >> > > although only rasmus can say f

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

Yasuo Ohgaki <[EMAIL PROTECTED]> wrote: > 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. although only rasmus can say for sure, i'd say you are assumin

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

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

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

Yasuo Ohgaki wrote: >>> Case of names can be easily converted by program. >> do you think it will be easy in this situation?: > I'm well aware of cases auto conversion is difficult. thats not what "can be easily converted" implied ... >> and, by the way: what kind of a program is going to conve

[PHP-DEV] Re: Case sensitivity: Conclusion(?)

Hartmut Holzgraefe wrote: > Yasuo Ohgaki wrote: > >> Case of names can be easily converted by program. > > > do you think it will be easy in this situation?: I'm well aware of cases auto conversion is difficult. > and, by the way: what kind of a program is going to convert this? For windows,