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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109fba,953e1a6689d791f6 X-Google-Attributes: gid109fba,public X-Google-Thread: fac41,953e1a6689d791f6 X-Google-Attributes: gidfac41,public X-Google-Thread: 103376,953e1a6689d791f6 X-Google-Attributes: gid103376,public From: donh@syd.csa.com.au (Don Harrison) Subject: Re: Eiffel and Java Date: 1996/11/04 Message-ID: #1/1 X-Deja-AN: 194245693 sender: news@syd.csa.com.au x-nntp-posting-host: dev11 references: <1996Oct31.202857.3481@merlin.hgc.edu> organization: CSC Australia, Sydney reply-to: donh@syd.csa.com.au newsgroups: comp.lang.eiffel,comp.lang.ada,comp.lang.c++ Date: 1996-11-04T00:00:00+00:00 List-Id: James McKim writes: :>eg. class SET_OPS :> ... :> union (a, b: SET): SET is ... :> intersection (a, b: SET): SET is ... :> ... :> end :In an article in the 10/94 issue of JOOP, Richie Bielak and I argued that :such features should really be creation routines in class SET. Good idea. (This article is titled "Let there be objects"). This looks like it would apply to most situations including creation types different from the parameters. It also preserves the philosophy of side-effect-free functions which my example violated. :( :IMHO, the dot notation and the desire for symmetry are almost orthogonal :issues. For better or for worse many library classes for languages that support :the dot notation have chosen to design intrinsically symmetric operations in :an asymmetric way, but that is not the only way. Agree. Good designs should preserve symmetry. Don. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Don Harrison donh@syd.csa.com.au