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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,4cd85c8656c704b6 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-12-03 06:29:04 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!hammer.uoregon.edu!skates!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Style question: deep inheritance Date: 03 Dec 2002 09:21:53 -0500 Organization: NASA Goddard Space Flight Center (skates.gsfc.nasa.gov) Message-ID: References: <5463bc76.0212030344.712c30aa@posting.google.com> NNTP-Posting-Host: anarres.gsfc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: skates.gsfc.nasa.gov 1038925995 10934 128.183.235.92 (3 Dec 2002 14:33:15 GMT) X-Complaints-To: usenet@news.gsfc.nasa.gov NNTP-Posting-Date: 3 Dec 2002 14:33:15 GMT User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.ada:31380 Date: 2002-12-03T14:33:15+00:00 List-Id: David95038@aol.com (David Kristola) writes: > So, portal > specific operations can be found in > SAM.Entities.Things.Portals. The three (and > counting) specializations of Portals are only > referenced once to initialize them and let them > register themselves into the system. I could use > renames to flatten out the majority of references > (package SAM.Portals renames > SAM.Entities.Things.Portals;), but you can't > inherit from a rename, so the actual children are > still deeply nested. The long package names > usually mean long file names. This could become a > portability problem. Any compiler implementation that limits file names must still allow long package names, and therefore provide a mechanism to map between them. Therefore I don't see how this could become a portability problem, any more than any file naming convention is a portability problem. A system should be a simple as possible, but no simpler. Your package names reflect the actual organization of the system; that's a benefit :). Sometimes, you can inherit from a type in a sibling package, rather than in a child package. So perhaps SAM.Portals is the _right_ package name in the first place? -- -- Stephe