You are here: Re: Case sensitivity in programming languages. « PHP Programming Language « IT news, forums, messages
Re: Case sensitivity in programming languages.

Posted by Tony Marston on 09/28/92 11:55

"Shelly" <sheldonlg.news@asap-consult.com> wrote in message
news:CF8Ag.3576$0e5.3548@newsread4.news.pas.earthlink.net...
>
> "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.

It is, and always has been my opinion that case sensitivity is a bad thing
because it creates more problems than it solves.

> You have yet to demonstrate **WHY** you believe it produces errors.

Instead of repeating myself I shall point you to
http://www.tonymarston.net/php-mysql/case-sensitive-software-is-evil.html

> Frankly, any time I even mistyped a name, the compiler barfed out that
> this was an undeclared variable or method.

Great. So your compiler did not allow you to reference anyhing in a
different case. But did it actually allow you to create several variabes or
methods with exactly the same spelling but different case? If the language
does not allow it, then there is no real problem. It only becomes a problem
when the language DOES allow it.

> 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.

Most languages don't use case to identify wheter something is a constant,
variable, function, or method, so the use of case is irrelevant.

> 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.

But people won't complain unless they hit problems, and I've seen complaints
from programmers who have suddenly been hit with a bug that turns out to be
case-related. I still hold the opinion that case sensitivity causes problems
instead of solving them, and I have seen no evidence to the contrary.

--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org

 

Navigation:

[Reply to this message]


Удаленная работа для программистов  •  Как заработать на Google AdSense  •  England, UK  •  статьи на английском  •  PHP MySQL CMS Apache Oscommerce  •  Online Business Knowledge Base  •  DVD MP3 AVI MP4 players codecs conversion help
Home  •  Search  •  Site Map  •  Set as Homepage  •  Add to Favourites

Copyright © 2005-2006 Powered by Custom PHP Programming

Сайт изготовлен в Студии Валентина Петручека
изготовление и поддержка веб-сайтов, разработка программного обеспечения, поисковая оптимизация