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,c4a14ea3a6faca74 X-Google-Attributes: gid103376,public From: Tucker Taft Subject: Re: Generic abstracts Date: 1999/11/30 Message-ID: <38444F24.F41BE126@averstar.com>#1/1 X-Deja-AN: 555035105 Content-Transfer-Encoding: 7bit Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.burl.averstar.com References: <3842BFFB.70B08603@averstar.com> <3842E945.AFBCCE17@averstar.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: AverStar (formerly Intermetrics) Burlington, MA USA Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-11-30T00:00:00+00:00 List-Id: Robert A Duff wrote: > > Tucker Taft writes: > > > However, at the moment only "overloadable" things (i.e. subprograms > > and enumerals) are inheritable, and that has some nice properties. > > I don't see the connection between overloadable and inheritable. By restricting inheritance to overloadable things, you don't get collisions when you have two derived types in the same scope, since overloadables won't hide each other unless they have identical types, which can't happen when defining a new derived type. > > By the way, I have wanted to write overloaded generic functions in the > past... I can't help you with that today ;-). > > - Bob -- -Tucker Taft stt@averstar.com http://www.averstar.com/~stt/ Technical Director, Distributed IT Solutions (www.averstar.com/tools) AverStar (formerly Intermetrics, Inc.) Burlington, MA USA