Case sensitivity/insensitivity
Bjorn Pettersen
bjorn at roguewave.com
Sat May 20 19:05:09 EDT 2000
Will Rose wrote:
>
[snip]
>
> For a single data point, I'm English (tho' German was my first language,
> which spoils the 'statistics' a bit). I don't think case-sensitive/
> insensitive varies with nationality; I've run across similar arguments
> in file-naming contexts (eg. Unix case-sensitive/case-preserving, and
> Microsoft long filenames case-insensitive/case-preserving). Some
> people just do see the tokens 'token' and 'Token' as being identical,
> and are very irate if their behaviour differs; others, like me, see
> them as different and hate the additional complexity of trying to
> memorise possible matches. (A bit like the 6-character limit on old
> linkers...). I don't know why people have these two different approaches,
> but it seems to be something fundamental in their use of language.
This brings up another interesting point... I'm assuming the subjects
from the Alice project/research would also prefer:
'token' == 'Token'
to return true. Perhaps we could add something like:
a = b # they're pretty similar
a == b # they're the same modulo case
a === b # they're the same including case
a ==== b # same meaning as current 'is' for consistency
add-<wink>s-until-you're-confident-I'm-joking'ly y'rs
-- bjorn
More information about the Python-list
mailing list