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=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID, RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,f66d11aeda114c52 X-Google-Attributes: gidfac41,public X-Google-Thread: 103376,f66d11aeda114c52 X-Google-Attributes: gid103376,public From: "Veli-Pekka Nousiainen" Subject: Re: Building blocks (Was: Design By Contract) Date: 1997/09/09 Message-ID: <01bcbd1d$54dcf7c0$108142c1@Yeif-1.eiffel.fi>#1/1 X-Deja-AN: 270979836 References: <5ulurp$aj8$1@miranda.gmrc.gecm.com> <5un58u$9ih$1@gonzo.sun3.iaf.nl> <5v0bph$n98$2@miranda.gmrc.gecm.com> Organization: AMT Oy Newsgroups: comp.lang.ada,comp.lang.eiffel Date: 1997-09-09T00:00:00+00:00 List-Id: Unsafe? what is unsafe in Eiffel inheritance? And what is the fix? I have joined in much too late... VP Brian Rogoff wrote in article ... > Eiffel's inheritance is based on a theoretical model which later turned out > to be unsafe. A (theoretical) fix was proposed, and never implemented. And > now we have another theoretical fix. So much for Eiffel theoretical > models! :-) > > -- Brian >