Fabricio Araujo wrote:

> On Wed, 23 Mar 2005 12:01:33 +0100, Kjell Rilbe wrote:
> Why you can't accept the fact that case sensitive idents can create
> very annoying and obscure programming errors? A sleepless night is
> just enough to this.
> These errors simple doesn't exist in case insensitive idents.

I can't accept the fact that such simple errors as simple typos could
cause such big problems as to losing sleep over it. No. I can't.

In Delphi, if you do a typo (other than wrong case, which Delphi
ignores), it will be caught as soon as you try to compile. You correct
it and try again. Problem solved in less than 10 seconds.

In C++, if you do a typo (including wrong case), it is also caught as
soon as you try to compile. Due to C++ complexity the error message
might be slightly more difficult to decipher, but once that problem is
solved you just correct the typo and try again. Problem probably solved
in less than a minute.

In SQL, if you do a typo in a query, it will be caught with a usually
pretty clear and helpful error message the first time the query is
prepared. You correct the typo and try again. If you change a query,
you'd better try to execute it at least once before putting it into your
production environment, otherwise you're a lunatic. If you do, you will
find the typo and correct it. Problem solved in less than a minute.

For SP:s, it's even better, because then the typo will be detected by
the SP compiler immediately when you try to (re)create the SP. Problem
solved in 10 seconds.

In all these scenarios I just can't see why case typos would cause such
endless extra problems compared to any other kind of typo. I just can't.
Feel free to enlighten me.

Kjell
--
--------------------------------------
Kjell Rilbe
Adressmarknaden AM AB
E-post: kjell.rilbe@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64