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, MSGID_RANDY 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: dennison@telepath.com Subject: Re: pointers & OOP Date: 1999/05/07 Message-ID: <7gv765$ioc$1@nnrp1.deja.com>#1/1 X-Deja-AN: 475207691 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-Http-Proxy: 1.0 x12.dejanews.com:80 (Squid/1.1.22) for client 204.48.27.130 Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Fri May 07 17:16:59 1999 GMT Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.5 [en] (WinNT; I) Date: 1999-05-07T00:00:00+00:00 List-Id: In article <3731fa3d.12295232@news.pacbell.net>, tmoran@bix.com (Tom Moran) wrote: > >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. OTOH, suppose you > really wanted procedure Internal_Updating to be visible to Son and > Daughter but *absolutely not* to any other package masquerading as > Parent.Prodigal_Son. Then you'd be forced to put Son and Daughter > inside the same package as Root (unless you went to a lot of trouble > with "doorman" routines). That still doesn't protect against Parent.Prodigal_Son, unless you also put that common routine in the package body. -- T.E.D. -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own