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,c703c7ba8401cbb6 X-Google-Attributes: gid103376,public From: Brian Rogoff Subject: Re: signatures Date: 1999/08/01 Message-ID: #1/1 X-Deja-AN: 507714392 References: <7o1kbb$2ku$1@bgtnsc01.worldnet.att.net> Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: nntp1.ba.best.com 933540173 201 bpr@206.184.139.136 MIME-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-08-01T00:00:00+00:00 List-Id: Well, they force your types to be tagged, and to inherit from the abstract tagged type on which your subprograms operate; this is something generic signature packages don't do unless you want them to. If I had my druthers, the next version of Ada would have something like Java interfaces, GNU C++ signatures, or Sather types/abstract-classes, in addition to the module signatures Ada has now. This introduces even more structural subtyping into Ada, but who said life was simple? :-) -- Brian On Sun, 1 Aug 1999, James S. Rogers wrote: > While on the subject of signatures, do not overlook abstract subprograms. > Abstract subprograms strictly enforce a signature without enforcing any > specific impelementation. > > Jim Rogers > Colorado Springs, Colorado > > > >