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,c8fd02a2b1be456a X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-19 15:00:24 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!pipex!uknet!cix.compulink.co.uk!usenet From: usagi@cix.compulink.co.uk ("Jim Wall") Subject: Re: Type extension with GNAT Message-ID: Organization: Jimbo References: Date: Sun, 19 Mar 1995 22:04:39 GMT X-News-Software: Ameol Date: 1995-03-19T22:04:39+00:00 List-Id: Erm, I get the feeling that you've tried something like: type One is tagged record A : ? B : ? end record; procedure A ( a : ?; b : ? ); type Two is new One with C : ? end record procedure A ( a : ?; b : ?; c : ? ); ???? assuming this (and forgive the pseudo-code) then, then what you're after is simply procedure A ( AA : One ); and procedure B ( BB : Two ); Here B If this is so, I suggest that if your original 'point' procedure were to accept the actual type Two_D_Point and the version for Three_D_Point (being the extended Two_D_Point) then the problem wouldn't arise.