Re: read on a do loop

Just to let you know, the backup didn't work the other night.  Had a <> 
where it should have been =.  Or maybe it was forgotten in a conversion 
from dou to dow?  Anyway, I ended up with an infinite loop.
         dow ReadEBkplib(BackupGroup)=0;  // This is the final, and 
working, way

To flog some more dead horses:

1 - As I stated previously, I like returning the actual read's %status 
instead of a logical true/false to give me the granularity of actually 
checking why the read failed.  (If I choose to care.)  I don't like to 
assume it was only because of EOF.  Could be because some read trigger 
blew up or any number of items that most programmers don't check for.

2 - I too like using a debuggable return variable in the subprocedure
       ReturnVar=%status(bkplib);
       return ReturnVar;
I agree that it would be nice to debug the bif's.  But in the RPG request 
vernacular, this might be one of those $100 requests.

3 - Doing the read in a subprocedure and using that on the dow loop does 
allow me to
    a - Not have both a priming read and a loop read
    b - Makes an iter work without an infinite loop

Rob Berendt