|
|
Posted by Wayne on 12/22/05 22:31
On 22 Dec 2005 07:54:07 -0800, tony@marston-home.demon.co.uk wrote:
>> But I didn't say $FOO or $Foo. I said $foo and $foO!
>
>Any programmer who deliberately mixes case like that is a candidate for
>the unemployment queue.
So then, why should the programming language allow it?!?
>The majority of programmers that I have worked with on
>case-insensitive languages do NOT like being told that case is suddenly
>important, that you must use one in preference to the other.
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.
Either case isn't important and programmers can mix case at will or
case is importantant. Give me one good reason why the language should
not enforce solid industry practices and keep poor unknowning
programmers out of the unemployment queue?
>*this* way or *that* way from now on everybody MUST do it *that* way
>for no other reason than to be consistent.
You just argued for that consistency in the first line of your post.
>> 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?
>And to a person who has been using case-insensitive compilers for 30
>years they are the same.
Sadly, you're in the minority. Majority rules.
Navigation:
[Reply to this message]
|