Re: Another problem with stream reading.

[David Bolen <db3l@fitlinxx.com>]

"Randy Brukardt" <randy@rrsoftware.com> writes:

> Janus/Ada, at least, will generate code for your type byte as if it is
> unsigned (that has necessary for Ada 83, which had no unsigned types at
> all), with all of the checking. But where the language requires the base
> type (such as in streams), we have to use signed 16-bits.
> 
> The place this matters, of course, is for the largest unsigned type. If
> you declare
>             type Unsigned is range 0 .. (2**32)-1;
> in Janus/Ada for Windows, you'll get an error, because there is no
> signed base type large enough to fit it.

How would you typically work around this, if you really wanted to be
working with 32-bit unsigned quantities in your code?  If there's no
signed base type large enough (sans 64-bit support presumably) would
you have to implement your own set of operations on, say, a data type
made out of two 16-bit values?

--
-- David
-- 
/-----------------------------------------------------------------------\
 \               David Bolen            \   E-mail: db3l@fitlinxx.com  /
  |             FitLinxx, Inc.            \  Phone: (203) 708-5192    |
 /  860 Canal Street, Stamford, CT  06902   \  Fax: (203) 316-5150     \
\-----------------------------------------------------------------------/