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: fac41,c52c30d32b866eae X-Google-Attributes: gidfac41,public X-Google-Thread: 103376,2ea02452876a15e1 X-Google-Attributes: gid103376,public X-Google-Thread: 1108a1,c52c30d32b866eae X-Google-Attributes: gid1108a1,public From: donh@syd.csa.com.au (Don Harrison) Subject: Re: Real OO Date: 1996/04/24 Message-ID: #1/1 X-Deja-AN: 151117734 sender: news@assip.csasyd.oz references: organization: CSC Australia reply-to: donh@syd.csa.com.au newsgroups: comp.lang.eiffel,comp.lang.ada,comp.object Date: 1996-04-24T00:00:00+00:00 List-Id: I wrote: :Jon S Anthony writes: : ::In article donh@syd.csa.com.au (Don Harrison) writes: [...] ::> : And the reason it is a problem ::> :is that Eiffel source does not have as much semantic information in it ::> :in this area. ::> ::> What might that be? :: ::Specifically, the distinction and use of the difference between class ::and type. The funny thing is, all this brouhaha about system validity ::concerns this distinction and an attempt to try to separate them ::again. : :No. This is not why. It's due to the distinction between static and dynamic :types. Correction. In the case of catcalls resulting from a change of routine signature, the problem arises when calls are attempted using a combination of objects which have incompatible dynamic types wrt the call. eg. surgeon.cut (carving_knife), when you really want surgeon.cut (scalpel) Most patients would prefer that the former is excluded :-). Don.