home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.object:3029 comp.lang.eiffel:993
- Newsgroups: comp.object,comp.lang.eiffel
- Path: sparky!uunet!munnari.oz.au!metro!graham
- From: graham@maths.su.oz.au (Graham Matthews)
- Subject: Re: Class methods (was: Re: How to design a data structure library)
- Message-ID: <graham.712278529@galois>
- Sender: graham@maths.su.oz.au
- Nntp-Posting-Host: galois.maths.su.oz.au
- Organization: Sydney University Computing Service, Sydney, NSW, Australia
- References: <1992Jul23.123609.11699@bony1.bony.com> <5618@vexpert.dbai.tuwien.ac.at> <GEOFF.92Jul27100601@wodehouse.flash.bellcore.com>
- Date: Mon, 27 Jul 1992 23:08:49 GMT
- Lines: 23
-
- (Geoffrey Clemm) writes:
- >I believe you missed the central point of Richie's article, namely that
- >Eiffel 3.0 has a clean way of handling this situation, to quote:
- >In article <1992Jul23.123609.11699@bony1.bony.com> richieb@bony1.bony.com (Richard Bielak) writes:
- >> Given this, the above call to "union" would be written like this
- >> (using Eiffel 3 syntax):
- >> !!c.union (a,b);
- >> Which I think is better.
- >With which I completely agree. This avoids the unpleasant assymetry
- >of c:=a.union(b).
-
- Personally I think this is just awful. I want to write
-
- c := a + b; OR
- c := a union b;
-
- Any other notation is completely non-suggestive.
-
- graham
- --
- Graham Matthews And it's true we are immune
- Pure Math, Uni.Sydney, Oz When fact is fiction and T.V. is reality
- graham@maths.su.oz.au
-