case sensitivity and XML

gmc333 at my-deja.com gmc333 at my-deja.com
Tue May 30 16:47:49 EDT 2000


In article <bQA$9LA3BQL5EwmF at gol.com>,
  Ian Parker <parker at gol.com> wrote:
> In article <392B40F0.324E0189 at cosc.canterbury.ac.nz>, Greg Ewing
> <greg at cosc.canterbury.ac.nz> writes
> >Fredrik Lundh wrote:
> >>
> >> so why not enforce these rules, just like we're enforcing the
> >> indentation rules:
> >>
> >>     >>> class foo:
> >>     SyntaxError: Class name should be Foo
> >
> >There are some precedents for this. Smalltalk requires
> >global variable names to start with a capital. HUGS
> >distinguishes type names from other names by whether
> >they start with a capital. Some Eiffel compilers chide
> >you if you don't spell class names in ALLUPPERCASE and
> >other names in alllowercase.
> >
>
> I don't think I could return to programming in a language that
> _required_ capitalisation or uppercase to indicate the purpose or
> function of some name.  I'm reminded of old Basic where a string was
> indicated with a $ or somesuch.  Isn't that a little like Perl.
Almost
> Hungarian.
>

Actually, the standard in Eiffel is for everything to be case-
insensitive. Some compilers like SmallEiffel
(http:\\smalleiffel.loria.fr) issue warnings by default for name case
inconsistencies, but this can be turned off.

And yes, a '$' prefix for vars is very Perl-ish. And I agree it's a
syntactic grotesquery.

Greg


Sent via Deja.com http://www.deja.com/
Before you buy.



More information about the Python-list mailing list