RE: how to create unsigned hexadecimal initial value -- MI400

No Peter, I disagree.

H" is signed.  The fact that the BIN variable is unsigned is not material,
that doesn't change the signed nature of H".

In this case, the value used to initialize the unsigned variable is, by
definition, a signed value.  If I got it right, Bob is saying that if you
want to initialize an unsigned BIN then you cannot use H" for all possible
values of the unsigned BIN.  In some cases, you will have to use X".

Here is another way to look at this.  You can have it the way that you want.
Write your own program to preprocess the MI source.  When you detect the
example that Gene gave us, you will have to rewrite the code to X" or it
will not compile.  That means, "As silly as the rule is, it is enforced
perfectly.  Therefore it is a real rule and we have to respect it."

In your reply, you say that H'80000000' is signed.  That is what Bob said.
I haven't had to do this in a long time - is H'80000000' equal to -1 or some
very large negative number?

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-----Original Message-----
From: owner-mi400@midrange.com [mailto:owner-mi400@midrange.com]On
Behalf Of Peter Lunde
Sent: Thursday, August 24, 2000 8:37 PM
To: MI400@midrange.com
Subject: RE: how to create unsigned hexadecimal initial value


I still think it IS a bug.

You mean an unsigned number cannot be more than H"7FFFFFFF"?

That is a bug.

Unsigned numbers should be able to range from H"00000000" to H"FFFFFFFF".

Signed numbers range from H"80000000" to H"7FFFFFFF".

Peter.

>From: "Richard Jackson" <richardjackson@richardjackson.net>
>Reply-To: MI400@midrange.com
>To: <MI400@midrange.com>
>Subject: RE: how to create unsigned hexadecimal initial value
>Date: Thu, 24 Aug 2000 15:37:02 -0600
>
>Bob:
>
>So, the problem was in trying to initialize an unsigned value with a signed
>value and it isn't a bug when that doesn't work.
>
>Feeling my way somewhat cautiously here, then the code is working as
>designed but the error message didn't completely explain the problem that
>the PRM/translator was having with the initialization value.  What do you
>think of that statement?
>
>For what it's worth, until someone else pointed up the H" situation, I was
>seeing X".  My comment that the behavior was a bug was based on seeing the
>X" string.  It probably wouldn't have made any difference - I probably
>would
>have assumed that X" and H" had the same semantics - but that specification
>difference is not intuitively different.  Wheels within wheels :)
>
>Thanks for helping with this.  Do you have a machine readable MI manual?
>
>Richard Jackson
>mailto:richardjackson@richardjackson.net
>http://www.richardjacksonltd.com
>Voice: 1 (303) 808-8058
>Fax:   1 (303) 663-4325

_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

Share information about yourself, create your own public profile at
http://profiles.msn.com.

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---