|
|
Posted by Wayne on 10/15/37 11:35
On Sat, 24 Dec 2005 22:48:06 -0000, "Tony Marston"
<tony@NOSPAM.demon.co.uk> wrote:
>By mixing case I mean mixing case in the same word. Some organisations like
>all upper case, some like all lower case, but NOBODY likes a mixture of case
>in the same word. That is the difference.
Ummm.. camelCase is used ALOT. In fact, camelCase is now becoming
the standard for PHP. avariablelikethisisveryhardtounderstand.
itsMuchEasierToSayThingsWithSomeCapitals.
>>>> >> trouble will all caps or the first letter capitalized. What about
>>>> >> the
>>>> >> difference between setsLower() and setSlower()? To a human reader
>>>> >> those have different meanings,
>>>> >
>>>> >Not to me, they don't.
>>>>
>>>> So lets say we're in a case-insensitive language and the function I
>>>> described above is listed in the program with both those cases. Tell
>>>> me, please, what does that function do?
>>>
>>>The function name is listed only once, but it can be invoked in either
>>>upper or lower case.
>>
>> You didn't answer my question! -5 points for you!
>
>You name me any language that has the same function name listed more than
>once in a different case.
What, you cannot image an application with both setsLower() and
setSlower() functions? Or at least something similar...
>Any language that deliberately allows the same variable or function name to
>exist in more than one case, and to have different meanings for each
>combination of case would be immediately slammed as being a VERY BAD
>language.
Wow. You just said that every single modern programming language is
VERY BAD. Why should we listen to your opinions?
>If a language enforces case-sensitivity by auto-correcting each
>name as you key it in, that is acceptable
The last language that did that -- Visual Basic -- is now dead. It
was case-insensitive but corrected the case to the declared casing.
Merry Christmas,
Navigation:
[Reply to this message]
|