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: 103376,dbf84a1c2794f4fb X-Google-Attributes: gid103376,public From: Ken Garlington Subject: Re: packages and private parts Date: 1997/02/08 Message-ID: <32FCE654.677A@lmtas.lmco.com>#1/1 X-Deja-AN: 217452221 references: <32FB27FF.794BDF32@innocon.com> content-type: text/plain; charset=us-ascii organization: Lockheed Martin Tactical Aircraft Systems mime-version: 1.0 newsgroups: comp.lang.ada x-mailer: Mozilla 3.01Gold (Win95; U; 16bit) Date: 1997-02-08T00:00:00+00:00 List-Id: Tucker Taft wrote: > > In my view, the point of encapsulation and information hiding is > not really to "hide" something, or to prevent it from being > changed (or "destroyed' ;-). Rather it is to make it easier to find all > code that depends on a particular implementation choice, so that > when the implementation is inevitably changed, you can track down all the > potentially affected code and fix it as necessary. This is also a primary motivation for the use of encapsulation/IH in the Software Productivity Consortium's ADARTS methodology, which we've used with some success. Based on my limited Ada 95 experience to date, I've found that child packages support system integrity, not threaten it. -- LMTAS - The Fighter Enterprise - "Our Brand Means Quality" For job listings, other info: http://www.lmtas.com or http://www.lmco.com