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,5394d9ca5f955366 X-Google-Attributes: gid103376,public From: John Robinson Subject: Re: pointers & OOP Date: 1999/05/10 Message-ID: #1/1 X-Deja-AN: 476234597 X-NNTP-Posting-Host: jr-and-assoc.demon.co.uk:194.222.150.244 References: <$DL10CAsSgL3Iwj3@jr-and-assoc.demon.co.uk> <7gn7gr$fr5$1@nnrp1.dejanews.com> <3731d200.1993345@news.pacbell.net> <3731fa3d.12295232@news.pacbell.net> X-Trace: news.demon.co.uk 926355266 nnrp-10:28063 NO-IDENT jr-and-assoc.demon.co.uk:194.222.150.244 MIME-Version: 1.0 Newsgroups: comp.lang.ada X-Complaints-To: abuse@demon.net Date: 1999-05-10T00:00:00+00:00 List-Id: In article <3731fa3d.12295232@news.pacbell.net>, Tom Moran writes >>Use parent-child structuring. Internal_Updating is a protected >>operation. I would still consider this to be a one to one mapping, >>although I don't use parent-child packages unless I have to. > If you'll allow child packages as "separate packages" it certainly >makes "1-1 packages/classes" a lot less draconian. My goal is to physically separate the implementation of behaviour associated with distinct concepts within the application domain. I believe this is achieved by this mapping, although again I try to avoid parent-child packages as much as possible since, as an encapsulation mechanism, they clearly have drawbacks. -- John Robinson John Robinson & Associates www.jr-and-assoc.demon.co.uk