From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,f66d11aeda114c52
X-Google-Attributes: gid103376,public
X-Google-Thread: fac41,f66d11aeda114c52
X-Google-Attributes: gidfac41,public
From: dnew@zloty.fv.com (Darren New)
Subject: Re: Design By Contract
Date: 1997/08/28
Message-ID: <5u4a2a$orh@newshub.atmnet.net>#1/1
X-Deja-AN: 268770241
References: <872172435.980@dejanews.com> <3403C44F.2424@erols.com>
 <5u3c6v$gtf$2@miranda.gmrc.gecm.com> <34058808.3BF@pseserv3.fw.hac.com>
Organization: FIRST VIRTUAL Holdings Inc.
Newsgroups: comp.lang.ada,comp.lang.eiffel
Date: 1997-08-28T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <34058808.3BF@pseserv3.fw.hac.com>,
W. Wesley Groleau x4923 <wwgrol@pseserv3.fw.hac.com> wrote:
>Paul Johnson wrote:
>> Now in my code I have something like:
>> 
>>    a: A;
>>    b: B;
>
>Is this legal Eiffel?  If so, put case insensitivity on the list of
>Ada's advantages.
>
>Unless Eiffel demands upper case for types/classes and lower case
>for variables/constants.  In that case, it's even, i.e., the 
>distinction introduces some benefits but also some problems.

Uh, no. That's not the point.

In Eiffel, there's certain syntactic places the name of a class can appear,
and certain syntactic places the name of a variable can appear, and the
two don't overlap.  Hence, the case distinction is irrelevant.

This is like saying in C

struct x { struct x * next; int data; }
struct x next;
[...]
next = next->next;

Now, granted, in this case it's probably bad style, but there's no confusion
that the first two "next" references are to the variable and the third is
to the structure member.

Same idea in the Eiffel code.