|
|
Posted by Tony Marston on 12/17/53 11:55
"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:O4udnUg-gOAPmkzZnZ2dnUVZ_oWdnZ2d@comcast.com...
> Tony Marston wrote:
>> "Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
>> news:p9CdnaiGK78Gt1LZnZ2dnUVZ_sqdnZ2d@comcast.com...
>>
>>>Tony Marston wrote:
>>
>> <snip>
>>
>>>>If you care to look back at previous posts in this thread you will see
>>>>where posters have argued the importance of different case in such
>>>>circumstances.
>>>>
>>>
>>>I haven't seen any of these languages you talk about, in this thread or
>>>anywhere else. You made a claim - now let's see you back it up.
>>
>>
>> Do our own dirty work. It was definitely said in a previous post that
>> some programmers, by convention and not a language requirement, use
>> different case to help differentiate between constants, variables,
>> functions and methods. PHP makes it very easy to differentiate between
>> those objects, so the use of different case is irrelevant. Yet those same
>> programmers are now saying "what was a convention is now a rule", and I
>> object to that.
>
> No, you made an unsubstantiated claim, then when I called you on it edited
> my post to completely change the context. To remind you of what your
> said:
My claim is not unsubstantiated. Read through the previous posts in this
thread and you will see for yourself.
>> Only in the minds of a few. Case sensitivity was introduced as a
>> programmer convention to get around the problem caused by some languages
>> which cannot identify the difference between a variable, a constant, a
>> function and a method.
>
> Again I ask you - substantiate this claim. Exactly which languages are
> these?
I don't know because I have never used those languages. Other posters in
this thread have stated that because their language (whatever it was) did
not provide any in-built means to differentiate between constants,
variables, functions and methods that they introduced the convention of
using different combinations of upper and lower case as a visual aid when
looking at the code. This was *not* a language requirement but a programmer
convention. Those same programmers are now trying to change this programmer
convention into a language requirement by insisting that the use of upper
and lower case is now enforced by the language.
That is one of my objections, that what started as a *programmer convention*
to get around the deficiencies of a particular language has bee elevated to
a *requirement* in all languages.
--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
Navigation:
[Reply to this message]
|