RE: working with the value of integer variables in debug

[Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>]

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.


-----Original Message-----
From: Buck Calabro [mailto:mcalabro@commsoft.net]
Sent: Tuesday, May 11, 1999 12:11 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: working with the value of integer variables in debug


I used scientific notation; BREAK 5 when index = 4.00e00  It was a stab in
the dark.  I did an ATTR index and it told me CARDINAL, 2 bytes.  I can
find no manual reference for this behaviour...

As for Mr Enzien trying to eval %found(filename), I don't believe this is
supported.  The only BIFs that the debugger seems to support are %SUBSTR,
%INDEX and %VAR.  Documentation seems scanty.

Buck Calabro

> -----Original Message-----
> From: Joel Fritz 
> Sent: Tuesday, May 11, 1999 11:50 AM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: working with the value of integer variables in debug
> 
> Here's an example of integer problems with a silly test program:
> *************************************************************************
> ***
>                             Display Module Source
> 
> Program:   INTLOOP        Library:   JEFTST         Module:   INTLOOP
> 
>      1           *MODULE ENTRY AND MAIN PROCEDURE ENTRY
>      2          1 Dindex            s              5u 0
>      3          2 Dnumber           s              5  0
>      4          3 C                   do        10            index
>      5          4 C                   eval      number = index
>      6          5 C                   enddo
>      7          6 C                   eval      *inlr = *on
>      8           *MAIN PROCEDURE EXIT
>  
> Bottom
> Debug . . .   BREAK 5 when index = 4
> *******Type compatibility error occurred.*******
> 
+---
| 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
+---
+---
| 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
+---