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,2c6139ce13be9980 X-Google-Attributes: gidfac41,public X-Google-Thread: f43e6,2c6139ce13be9980 X-Google-Attributes: gidf43e6,public X-Google-Thread: 1108a1,2c6139ce13be9980 X-Google-Attributes: gid1108a1,public X-Google-Thread: 103376,3d3f20d31be1c33a X-Google-Attributes: gid103376,public From: donh@syd.csa.com.au (Don Harrison) Subject: Re: Safety-critical development in Ada and Eiffel Date: 1997/07/14 Message-ID: #1/1 X-Deja-AN: 256801417 Sender: news@syd.csa.com.au X-Nntp-Posting-Host: dev50 References: <5q5p9o$2s4@typhoon.xnet.com> Organization: CSC Australia, Sydney Reply-To: donh@syd.csa.com.au Newsgroups: comp.object,comp.software-eng,comp.lang.ada,comp.lang.eiffel Date: 1997-07-14T00:00:00+00:00 List-Id: James Graves writes: :In article , :Don Harrison wrote: :> :> I suspect that you can also make an Eiffel reference access a statically :> allocated object (expanded type) using a standard class (MEMORY? someone may :> wish to confirm this). There would certainly be no technical obstacle to :> providing this capability if it doesn't already exist enabling you to :> statically allocate whatever memory you require if that's what you want :> (as in your application domain). :> : :You are not allowed to make a reference to an expanded object in Eiffel, :because of the information hiding principal. To be able to diddle with :another object's internal data could easily violate the class :invariant. Oops! Quite true. I agree the technique you suggest is better. Don. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Don Harrison donh@syd.csa.com.au