Re: AW: [PHP-DEV] 4.1 & Declaration Case Persistance

On Thu, 10 May 2001, Harald Radi wrote: >looking forward to getting php case sensitive i'm just wondering that Me too. >function names are exported mixed case in the com extension. >e.g. there's a COM_load() and a com_set(), is there a special reason for >this (zeev) ? This is just because some developers don't like to follow the guidelines. As, I quote, "it woulnd't be fun anymore" or "you can't force anyone". >another question: according to the CODING_STANDARDS file every function >should be lowercase, but how about exported classes ? is there a guidline >for this ? See above. --Jani >harald. > >> -----Ursprüngliche Nachricht----- >> Von: chuck@marina.horde.org [mailto:chuck@marina.horde.org]Im Auftrag >> von Chuck Hagenbuch >> Gesendet: Freitag, 04. Mai 2001 21:10 >> An: php-dev@lists.php.net >> Betreff: Re: [PHP-DEV] 4.1 & Declaration Case Persistance >> >> >> Quoting Colin Viebrock <colin@easyDNS.com>: >> >> > One "problem" with case sensitivity (perhaps) is that it may make some >> > scripts non-portable. >> >> That's a problem with it being an option, yes. I'd vote for just >> making php >> case sensitive, period. >> >> -chuck >> >> -- >> must... find... acorns... *thud* >> >> -- >> PHP Development Mailing List <http://www.php.net/> >> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net >> For additional commands, e-mail: php-dev-help@lists.php.net >> To contact the list administrators, e-mail: php-list-admin@lists.php.net >> >> > > >