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: 109fba,1042f393323e22da X-Google-Attributes: gid109fba,public X-Google-Thread: 1014db,1042f393323e22da X-Google-Attributes: gid1014db,public X-Google-Thread: 103376,1042f393323e22da X-Google-Attributes: gid103376,public From: jsa@alexandria (Jon S Anthony) Subject: Re: Any research putting c above ada? Date: 1997/05/02 Message-ID: #1/1 X-Deja-AN: 239041725 Distribution: world References: <5ih6i9$oct$1@waldorf.csc.calpoly.edu> <5j078b$b25$1@NNTP.MsState.Edu> <5j31lj$qnk@huron.eel.ufl.edu> <335F9D0E.41C67EA6@cacd.rockwell.com> <5jqvbj$bd9@mtinsc05.worldnet.att.net> <5k67fl$eit@mtinsc03.worldnet.att.net> Organization: PSI Public Usenet Link Newsgroups: comp.lang.c++,comp.lang.c,comp.lang.ada Date: 1997-05-02T00:00:00+00:00 List-Id: In article eachus@spectre.mitre.org (Robert I. Eachus) writes: > add state. The final answer was a compromise: > > type Bar is new Foo with null record; > > Three keywords to indicate that the type could have been extended, > but wasn't. There needs to be something, and a lot of us wanted "with > null;" instead of "with null record;" but that's what compromise is Actually, I've always had a simple question about this area. Why was the "record" bit included in tagged types at all?? Why not simply: type T is tagged x: ... y: ... ... end T; and type S is new T with ... end S; and as you say above type R is new T with null; Why was the "record" bit even there? It's not a big deal, but IMO the "record" part even is rather misleading - tagged things are very different in all sorts of ways from regular old record types and people can (and have - as evidenced by various threads in c.l.a) get tripped up by this. /Jon -- Jon Anthony Organon Motives, Inc. Belmont, MA 02178 617.484.3383 jsa@organon.com