RE: working with the value of integer variables in debug

It is bizarre.  I just kept trying data types until I found one that
worked.
I'd call it a bug.
The internal representation of unsigned int is just as you have presented
it - two bytes, no sign bit allocated.

Buck Calabro

> -----Original Message-----
> From: Joel Fritz 
> Sent: Tuesday, May 11, 1999 5:00 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: working with the value of integer variables in debug
> 
> Thanks, that's really bizarre.  I've tried attr and displaying the value
> as
> hex to try to find out what the debugger wanted to see, but using
> scientific
> notation seems to go against the definition of integers.  The debugger
> doesn't seem to care when I tried breaking on index = 4.15e00.
> 
> This brings up two questions:
>      1.  Bug or feature?
>      2.  What's the internal representation of an integer?  I assumed
> (silly, I know) that it was a binary             number so 4 in a 2 byte
> unsigned would be 00000000 00000100 or 0004 in hex.  The debugger says
> the
> hex              representation is 0004.
> 
> 
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---