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,1116ece181be1aea
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2003-09-24 04:43:09 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!peernews-us.colt.net!newsfeed.news2me.com!elnk-nf2-pas!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!stamper.news.atl.earthlink.net!newsread2.news.atl.earthlink.net.POSTED!not-for-mail
Sender: mheaney@MHEANEYX200
Newsgroups: comp.lang.ada
Subject: Re: Is the Writing on the Wall for Ada?
References: <wvbrad9emn3u.fsf@sun.com> <u3cez82oh.fsf@earthlink.net>
 <wvbr65jul87d.fsf@sun.com> <uhe3d7hmj.fsf@earthlink.net>
 <xXt9b.4926$U41.4024@nwrdny01.gnilink.net> <ud6e178aw.fsf@earthlink.net>
 <568ede3c.0309160929.1d0d3d95@posting.google.com>
 <3F67AFB9.7040001@attbi.com> <OJO9b.1195$U6.228@nwrdny03.gnilink.net>
 <3F6F0841.60607@attbi.com> <1064244399.683441@master.nyc.kbcfp.com>
 <jjuvmvoo493di1rpgm82c31r2qk0a8psr6@4ax.com> <ullsfvsoi.fsf@earthlink.net>
 <dij2nvc4c9gpkjfpkehr63ab0idue3c2ct@4ax.com>
From: Matthew Heaney <matthewjheaney@earthlink.net>
Message-ID: <u7k3ywgv2.fsf@earthlink.net>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 24 Sep 2003 11:43:08 GMT
NNTP-Posting-Host: 65.110.133.134
X-Complaints-To: abuse@earthlink.net
X-Trace: newsread2.news.atl.earthlink.net 1064403788 65.110.133.134 (Wed,
 24 Sep 2003 07:43:08 EDT)
NNTP-Posting-Date: Wed, 24 Sep 2003 07:43:08 EDT
Organization: EarthLink Inc. -- http://www.EarthLink.net
Xref: archiver1.google.com comp.lang.ada:42851
Date: 2003-09-24T11:43:08+00:00
List-Id: <comp.lang.ada>

Dmitry A. Kazakov <mailbox@dmitry-kazakov.de> writes:

> T_Set and NT_Set are unrelated types. So one cannot be a
> subtype/subclass of another. It means that I cannot write a
> NON-GENERIC program operating on both.

Your problem was to have an operation to traverse a container of
Element_Type, and to be able to reuse the same operation over a
container whose element type derives from Element_Type.

The solution I showed does that.  Whether it's generic vs. non-generic
shouldn't matter.