| Subject | Re: AW: [firebird-support] Use of double quoted names in Firebird |
|---|---|
| Author | Fabricio Araujo |
| Post date | 2005-03-26T17:57:49Z |
On Fri, 25 Mar 2005 21:28:29 +0100, Alexander Gräf wrote:
languages, like indentation.
Being such, anyone takes the case convention that of their convenience.
Case is just aesthetic.
like punch-card Cobol.
"Start that instruction in the column x and not go beyond y" - ah, Alex
I have more to do
than taking care of case of identifiers!!!!
Case insensitive languages is a advance. One source of headache less.
>The case-sensitive language. Case is just a convenience in computer
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Ivan Prenosil [mailto:Ivan.Prenosil@...]
>> Gesendet: Donnerstag, 24. März 2005 15:14
>> An: firebird-support@yahoogroups.com
>> Betreff: Re: [firebird-support] Use of double quoted names in Firebird
>>
>> If you write "avan", I will not know what you mean, but if
>> you write "ivan", "Ivan", "IVAN", I guess I will recognize
>> all of them.
>
>I'll recognize them, because I is uppercased for i. You're from czech republic, I'm from german, we both can
>recognize those letters. However, as Kjell stated, in *his* language (swedish), v and w do mean the same, as i
>does mean the same as I for us. You see my point? One rule says "i equals I", but no rule says "v equals w", only
>because americans are not used to think about v equaling to w. What about kyrillic? What about eastern languages? >What about those people in india? Do they even know about the concept of lower- vs. uppercase?
>> > People who are actually not able to remember the case of
>> their identifiers ...
>>
>> But its not only "their" identifiers, you can use lot of 3rd
>> party libraries, each one using its own "rules", one can have
>> mehod "doClose", the other "DoClose", and I personally have
>> more important things to remember than those _cosmetic_ variants.
>>
>
>But who is in error? The language which forces case-sensitive identifiers, or the library makers which do not
>adhere to naming conventions?
languages, like indentation.
Being such, anyone takes the case convention that of their convenience.
Case is just aesthetic.
>Rather than letting the parser forgive about case, it would make sense to force aI prefer that the parser forget about the case. Otherwise, it'll be
>unified naming scheme.
like punch-card Cobol.
"Start that instruction in the column x and not go beyond y" - ah, Alex
I have more to do
than taking care of case of identifiers!!!!
Case insensitive languages is a advance. One source of headache less.