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,48bbfdbc3683ed X-Google-Attributes: gid103376,public From: tmoran@bix.com (Tom Moran) Subject: Re: Tagged Rep Spec Date: 1999/06/15 Message-ID: <3766970e.273390@news.pacbell.net>#1/1 X-Deja-AN: 489942429 References: <7k5mop$n0i$1@nnrp1.deja.com> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.snfc21.pbi.net 929470671 207.214.215.92 (Tue, 15 Jun 1999 11:17:51 PDT) Organization: SBC Internet Services NNTP-Posting-Date: Tue, 15 Jun 1999 11:17:51 PDT Newsgroups: comp.lang.ada Date: 1999-06-15T00:00:00+00:00 List-Id: Though some compilers used to have troubles with this, it seems to work now on the compilers I've tried. Tag_Size : constant := 4; -- compiler dependent stuff! for Interrupt_Record_Type use record watchdog_warning at 0+Tag_Size range 0..0; utility_clock at 0+Tag_Size range 1..1; timer1 at 0+Tag_Size range 2..2; rs232 at 0+Tag_Size range 3..3; mailbox at 0+Tag_Size range 4..4; end record; As MDC points out, it's very compiler dependent and non-portable. Could you use type Inner_Record is ... -- not tagged for Inner_Record use ... type Interrupt_Record_Type is new ... with record Contents : Inner_Record; end record; Usually you need to give rep specs because you are dealing with external hardward or software that has its own ideas. Usually such hardware or software has no idea what a tag might mean, so you really would rather communicate with it via Inner_Record than via a tagged record. If you really need the tag, perhaps you should use Streams instead.