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,45a9122ddf5fcf5
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Rules for Representation of Subtypes
Date: 1996/09/27
Message-ID: <DyEr9F.40E@world.std.com>#1/1
X-Deja-AN: 185699233
references: <mheaney-ya023080002209961353500001@news.ni.net>
 <mheaney-ya023080002409960726040001@news.ni.net> <DyCF97.7zp@world.std.com>
 <mheaney-ya023180002709960713140001@news.ni.net>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.ada
Date: 1996-09-27T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <mheaney-ya023180002709960713140001@news.ni.net>,
Matthew Heaney <mheaney@ni.net> wrote:
>So the moral of the story is, if you're reading data off an interface, read
>it into a an object of a first named subtype without constraints.  ...

ANd make sure the first-named subtype matches the hardware data types.
E.g., use Interfaces.C.int.

- Bob