|
|
Posted by Wayne on 10/16/41 11:35
On 23 Dec 2005 01:15:37 -0800, tony@marston-home.demon.co.uk wrote:
>Wayne wrote:
>> Ok... so let me get this straight. First you say that mixing cases
>> is bad and then you say that programmers don't like being told that
>> case is suddenly important. Those two things are contradictory.
>
>What I'm saying is that some teams like their variable names in all
>upper case, while others like them all lower case. Either is
>acceptable, but mixing case in the same variable name is frowned upon
>by both camps.
Ok. But that was my point. What's the point of having
case-insensitivity if mixing cases is frowned upon. Clearly you only
want to one case spelling of a function or variable to be valid.
>> >> People have no
>> >> 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!
Saying that the programmer must go find the original declared version
of the function to determine what it does, doesn't answer the
question.
Navigation:
[Reply to this message]
|