|
|
Posted by Shelly on 10/05/70 11:54
"Tony Marston" <tony@NOSPAM.demon.co.uk> wrote in message
news:eapvkq$406$1$8300dec7@news.demon.co.uk...
>
> "Shelly" <sheldonlg.news@asap-consult.com> wrote in message
> news:C5Rzg.3201$0e5.561@newsread4.news.pas.earthlink.net...
>> Correction:
>>
>> I previously posted that modern languages have the goto but good
>> programmers (even not-so-good programmers) ddon't use it. I was wrong.
>> In Java the goto is an unimplemented keyword. I made that mistake
>> because, well, I can't remember the last time I used a goto.
>>
>> Shelly
>
> PHP also does not have an unstructured GOTO simply because the language
> authors see the potential for huge mistakes, and decided to leave it out
> to help protect the unwary programmer from making difficult-to-spot
> mistakes. It is my opinion that the introduction of case-sensitivity into
> software falls into the same category, therefore should be avoided
> wherever possible.
I will quote you from above: "It is my opinion". Well, most professional
programmers hold an opposing opinion. You may like tutti-frutti, but most
people like other flavors.
You started this thread with a rant about how case sensitivity **IS** a bad
thing and introduces errors. You have now backed off from that position to
the substatiable point that it is your **OPINION** that this is the case.
You have yet to demonstrate **WHY** you believe it produces errors.
Frankly, any time I even mistyped a name, the compiler barfed out that this
was an undeclared variable or method. No big deal. In **MY** OPINION, that
little incovenience is **GREATLY** outweighed by the ability to read someone
else's code and know right away what it is all about. Apparantly the vast
majority of professional programmers agree with me because that is the
direction in which all the newer languages are going -- even something as
new as PHP.
Shelly
Navigation:
[Reply to this message]
|