HP3000-L Archives

December 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Emerson, Tom # El Monte" <[log in to unmask]>
Reply To:
Emerson, Tom # El Monte
Date:
Mon, 11 Dec 2000 13:52:24 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines)
> -----Original Message-----
> From: Ken Hirsch [mailto:[log in to unmask]]
>  "Emerson, Tom # El Monte" <[log in to unmask]> wrote:
> >
> > now that I think about it, ^L is 12 decimal, or 0x0C in hex, which
> > is NOT a legal "COMP3" value
>
> You're forgetting the sign nibble.  A COMP-3 value of zero,
> or any positive
> number with a last digit of zero would have '0x0C' as its last byte.

>ack< I stand corrected -- most of the fields I deal with are usage DISPLAY,
and unsigned to begin with [we deal with positive numbers primarilly, and
the few cases where "negative" numbers are appropriate are already tagged
elsewhere in the record as being a "credit" value...]  This, of course, is
far more appropriate when dealing with cross-system data as there is no
ambiguity over little things like signs, byte order (little-endian vs.
big-endian) and the actual representation of digits.  [well, ok, I suppose
if you're considering EBCDIC vs. ASCII, there might be some confusion... ;)
]

ATOM RSS1 RSS2