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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Im Auftrag
>> von Chuck Hagenbuch
>> Gesendet: Freitag, 04. Mai 2001 21:10
>> An: [EMAIL PROTECTED]
>> Betreff: Re: [PHP-DEV] 4.1 & Declaration Case Persistance
>>
>>
>> Quoting Colin Viebrock <[EMAIL PROTECTED]>:
>>
>> > 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: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> To contact the list administrators, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
