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,555956c1cdd22308 X-Google-Attributes: gid103376,public From: Matthew Heaney Subject: Re: Help - Constructors - ASAP. Date: 1998/08/04 Message-ID: #1/1 X-Deja-AN: 377746051 Sender: matt@mheaney.ni.net References: <6p75qi$rcj@news.latnet.lv> <6pi4jq$j73$1@nnrp1.dejanews.com> <35C5C534.D773CAA2@elca-matrix.ch> <35C5FCD9.2EE39FE4@elca-matrix.ch> NNTP-Posting-Date: Tue, 04 Aug 1998 00:05:51 PDT Newsgroups: comp.lang.ada Date: 1998-08-04T00:00:00+00:00 List-Id: Mats Weber writes: >>> Another problem, which I think is even worse, is when some >>> operations of a type are generics (e.g. iterators), then these will >>> not be derived and you will have to get them from the package that >>> declares them. >> >> You can rename generic operations. > > But then, they keep the old parameter profile, the one with the type you are > deriving from, not the derived type. Bad. Ah, but then another rule of thumb applies. Since the generic operation isn't primitive anyway, you just make the tagged parameters class-wide. Then it will work for your derived types too.