|New Book: The School of Niklaus Wirth firstname.lastname@example.org (2000-10-31)|
|Re: New Book: The School of Niklaus Wirth email@example.com (Sebastian Moleski) (2000-11-01)|
|Re: New Book: The School of Niklaus Wirth Martin.Ward@durham.ac.uk (2000-11-05)|
|Re: New Book: The School of Niklaus Wirth firstname.lastname@example.org (Mikael Lyngvig) (2000-11-05)|
|Re: New Book: The School of Niklaus Wirth email@example.com (2000-11-07)|
|Re: New Book: The School of Niklaus Wirth firstname.lastname@example.org (jt) (2000-11-07)|
|case sensitivity (was: Re: New Book: The School of Niklaus Wirth) email@example.com (2000-11-07)|
|Re: New Book: The School of Niklaus Wirth firstname.lastname@example.org (2000-11-09)|
|Re: New Book: The School of Niklaus Wirth email@example.com (Gabor DEAK JAHN) (2000-11-11)|
|[11 later articles]|
|From:||Martin.Ward@durham.ac.uk (Martin Ward)|
|Date:||5 Nov 2000 20:45:19 -0500|
> humans tend to recognize names that differ solely in case without problems
Humans also recognise abbreviated names, nicknames, names with
spaces in them...
> Imagine that your mails, delivered via postal service, starts to
> bounce because you'd accidentally written "main Street" rather than
> "Main Street" (or the postal worker thinks you've written "main"
> rather than "Main")...
(1) The postal service has a lot more to worry about than
case differences. What if you wrote "Main St."? Would you want
mail addressed to "Mick Lyngvig" to bounce?
(2) A mathematician would be very surprised to find that "n" and "N"
are treated as the *same* symbol.
On the other hand, if your compiler is going to be case-sensitive,
don't do what one compiler did and convert all error messages
(including identifier names) to UPPER CASE!
Martin.Ward@durham.ac.uk http://www.dur.ac.uk/martin.ward/ Erdos number: 4
Return to the
Search the comp.compilers archives again.