× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: how to create unsigned hexadecimal initial value
  • From: "Richard Jackson" <richardjackson@xxxxxxxxxxxxxxxxxx>
  • Date: Fri, 25 Aug 2000 17:57:10 -0600
  • Importance: Normal

After all the work that you and Gene have done to inform me (by the way,
thanks for that), I think that I understand the design and implementation.
I happen to think that what it is doing is wrong.

I was brung up with the idea that a hex literal has no insignificant digits.
The type H literal doesn't follow that rule and I WOULD screw that up about
one half of the time.  I think I'll just stick to type X.

BTW, I also happen to think that RSLVSP should replace the contents of a
system pointer.  I have been hammered by that more than once because it is
not intuitive to me.

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 Leif Svalgaard
Sent: Friday, August 25, 2000 1:59 PM
To: MI400@midrange.com
Subject: Re: how to create unsigned hexadecimal initial value


From: Richard Jackson <richardjackson@richardjackson.net>
> I concur with your conclusion.  Based on what I have seen for the
> experiments that you and Gene have done, X' looks a lot more predictable
to
> me.  It might be interesting to figure out where the H' came from and who
> uses it.  Can any bugs be traced back to it challenging nature?

several of my examples are from my "bug book". This one in particular:

DCL DD NN BIN(2);
DCL DD XX CHAR(2) DEF(NN);

CPYNV  NN, -1;
AND(S) NN,H'0003';
CVTHC MSG-TEXT(1:4), XX;
CALLI SHOW-MESSAGE, *, .SHOW-MESSAGE;    <==== shows  0300    wrong

took me three days to figure out. I had to disassemble the code and actually
look at the RISC instructions to convince myself that it was the machine and
not me being wrong. It was particular nasty because no compiler error or
warning was issued.

+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.