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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID 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: jsa@alexandria.organon.com (Jon S Anthony) Subject: Re: Design By Contract Date: 1997/09/05 Message-ID: #1/1 X-Deja-AN: 270013617 References: Distribution: world Organization: PSINet Newsgroups: comp.lang.ada,comp.lang.eiffel Date: 1997-09-05T00:00:00+00:00 List-Id: In article nospam@thanks.com.au (Don Harrison) writes: > Especially since you haven't shown how you think child packages can > give some of what selective export has to offer. It's a bit > difficult to give an example of what they *don't* offer if it's not > clear what they *do* offer. See Patrick's example. The point is, private children provide a level of "selective export" (exporting their interfaces only to their parent's body and certain parts of the private subtrees). IME, this has been quite sufficient. Eiffel's selective export is really much more like the granularity you get (and the attendant problems from) C++ friendship. /Jon -- Jon Anthony OMI, Belmont, MA 02178, 617.484.3383 "Nightmares - Ha! The way my life's been going lately, Who'd notice?" -- Londo Mollari