On Wed, 23 Mar 2005 11:17:03 +0100, Kjell Rilbe wrote:

>
>Fabricio Araujo wrote:
>
>> Yeah... But UNICODE_FSS and internationalizaton is a very troubled
>> issue discussed to dismay here, architect and devel lists.
>
>I'd say that's just teething problems. Unicode in all it's flavors is
>not new, but wide-spread use is. A lot of people are still learning and
>many tools still have problems with it. These problems will go away.

hmmm.

>
>> Most developers here work on a one-man-house basis, Kjell. So not
>> looking for trouble is better... ;-)
>
>In all relevant aspects I'm a one-man business myself. But a typo is a
>typo is a typo. It should be caught in testing or even before testing
>(compilation).

Not if it don't change the working. If so, it's only a reading
inconvenience.

>> 1) But r vc R are mostly subtle and lead to logical errors.
>> 2) n vs M mostly generate SP or code compiling error.
> >
> > Debug time for 1) is MUCH higher than 2).
>
>With case sensitive identifiers, the difference you're describing would
>not exist. r and R would be exactly as different as n and m in the SP
>compiler's eyes.

When I said it above, I am considering case sensitive identifiers.

If the identifiers were case INsensitive 1) does not exist is just
a nuisance, don't affect at all the system.

Case sensitive identifiers is one of the reason most people hate
C/C++...