Why make a language case sensitive?
PM
vtbl.moorepe at memo.volvo.se
Tue Jul 18 11:42:19 EDT 2000
I don't see why ENFORCING case sensitivity precludes the use of naming conventions.
If the restriction was lifted, I think it would help in the development
phase, especially when it comes to guessing method names.
Later you could always go back and straighten anything glaring out, anyway.
I don't think that if things were relaxed you would find heaps of uGly
And WEird lAnguAge Usage. This could be dealt with, anyway.
With case anal-retention annoying errors and obfuscation (accidental by
a newbie or deliberate) are easier to create.
Oh I get it! :)
No seriously, I think there is a case for case relaxation. I say R e l
a x.
> If you're used to C++ (or Python or Java), which don't have
> to be Unix-based, then you quickly discover that a simple naming
> convention in your code makes for easy (cheap) maintenance and
> reuse...
>
> e.g.
>
> MyClass ... Class definition
> myClass ... Instance of class (or other 'variable')
> MYCLASS ... Constant (maybe an enumeration)
>
> Then, within a class, instance or variable name, mixed case aids
> readability:
>
> A = ... ? Old Basic ;-)
> mainwindowframeborderwidth = ... Caseless language (or poor C++)
> mainWindowFrameBorderWidth = ... IMHO better
>
> Take a look at example code for any of the major languages and I'm
> sure that you'll spot a trend... Of course, if you're an assembler
> programmer, then you probably don't care -- but even assemblers
> can be case sensitive :-)
>
> John
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
More information about the Python-list
mailing list