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,3d9f3074dc2c4699 X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: How to overload assignment in Ada 95? Date: 1996/12/11 Message-ID: <1996Dec11.164852.1@eisner>#1/1 X-Deja-AN: 203574758 distribution: usa x-nntp-posting-host: eisner.decus.org references: <58aclh$ssd@gaia.cc.gatech.edu> <1996Dec10.143635.1@eisner> x-nntp-posting-user: KILGALLEN x-trace: 850340940/24749 organization: LJK Software newsgroups: comp.lang.ada Date: 1996-12-11T00:00:00+00:00 List-Id: In article , bbalfour@std.caci.com (Brad Balfour) writes: > If the new type were defined as tagged private and only derived from A.F.C > in the private part, then any further derivation that wanted to call on > the operations inherited from A.F.C would have to be located in a child > package. For many cases that is delightful, but "frameworks" are often intended to be extended by clients. > FWIW, I happen to like the style which mirrors the inheritance hierarchy > in the child package hierarchy. But making the derivation public should not prevent one from mirroring the inheritance in the child package hierarchy. Even if enforcement by compiler is not acceptable, clarity is still nice. Larry Kilgallen