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,83d7c4caadb45100
X-Google-Attributes: gid103376,public
From: mfb@mbunix.mitre.org (Michael F Brenner)
Subject: Re: DECAda/VMS - calling GETJPI
Date: 1996/06/03
Message-ID: <4ouuuv$6hd@linus.mitre.org>#1/1
X-Deja-AN: 158232314
references: <31B2AF74.668E@dial.eunet.ch> <4ouo97$pe8@gcsin3.geccs.gecm.com>
organization: The MITRE Corporation, Bedford Mass.
newsgroups: comp.lang.ada
Date: 1996-06-03T00:00:00+00:00
List-Id: <comp.lang.ada>


Under Ada 95, assuming that unsigned_longword was defined as 
  type unsigned_longword is mod 2**64;

  or 

  type unsigned_longword is mod 2**32;

you could just assign it:

  integer_minus_1: integer := -1;
  x: unsigned_longword := unsigned_longword (integer_minus_1);

because Ada 95 modular types truncate numbers to their modular range
without giving a constraint_error.

However, if unsigned_longword is defined using one of the Ada-83
workarounds earlier in this thread, then the workarounds earlier in
this thread could be attempted, with appropriate tests to make sure
they are doing what you think they are doing.