Re: R: RPG Indicators

[boothm@xxxxxxxxxxxxxxxxx]

But Jon, his question raised the specter of the debugger.  How do we know 
the state of the %bif?
_______________________
Booth Martin
boothm@earth.goddard.edu
http://www.spy.net/~booth
_______________________




Jon.Paris@hal.it
Sent by: owner-rpg400-l@midrange.com
04/18/2000 03:04 PM
Please respond to RPG400-L

 
        To:     RPG400-L@midrange.com
        cc: 
        Subject:        Re: R: RPG Indicators




 >>  I come back to indicators.  What do you think about this?

I think that there is no reason to use indicators at all any more except 
where
dictated by the compiler (e.g. LOOKUP) and even then you don't have to 
_use_ the
indicator afterwards, it is only needed to qualify the operation.

I'm not sure why so many people seem to be confused over the use of 
%Found.  The
built-ins map on a one-to-one basis with the old indicators, so it is all 
very
straightforward.  %Found is only set by operations that can set the "No 
Record
Found" (NRF) indicator (e.g. CHAIN).  Since READC does not set the NRF 
indicator
it does not set %Found either.

The basic plan is this:

%EOF - set whenever the EOF indicator would have been set.

%Error - set when the (E) extender is used _and_ the error indicator would 
have
been set

%Found - the opposite of the NRF indicator - set when the indicator would 
have
been off and vice-versa
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: 
david@midrange.com
+---




+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---