|
|
Posted by Tony Marston on 08/04/06 14:47
"Jerry Stuckle" <jstucklex@attglobal.net> wrote in message
news:2KidnWwC8IHib0zZnZ2dnUVZ_v-dnZ2d@comcast.com...
> Tony Marston wrote:
<snip>
>>>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.
>>
>
> I have read every post here. Again - substantiate your claim. But you
> can't, because it isn't in this thread. Just another unsubstantiated
> claim you pulled out of your arse in a disparate attempt to bolster your
> losing arguments.
I repeat - 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.
> Typical troll - you can't fight facts so you try to make things up.
>
>>
>>>>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.
>>
>
> Ah, so now you say it was a convention, not the fact the language couldn't
> differentiate. Which is it, Tony? And which language? I still haven't
> seen anything here.
I did not say that the *language* could not differentiate, I said that the
*programmers* who read the code had that difficulty. That is why they
created a convention whereby different case was used for different objects.
The language itself did not care which case was used, nor did it use case in
the method employed by those programers. It was programmer choice, not a
language requirement.
> And what makes you think that "programmer convention" was elevated to a
> "requirement"? Or can you even prove that claim? I think now because
> they are completely unrelated.
The use of case to tell the difference between a constant, a variable, a
function and a method is bang promoted as a "standard" which should be
applied to ALL languages, even though it started out as a simple programmer
convention in one particular language.
--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
Navigation:
[Reply to this message]
|