× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. August 2005

Re: read on a do loop



Isn't that the way RPG has evolved?  Used to be we'd test an indicator set
on the Read statement for an end or error condition.  In that case the Read
and end/ error were one atomic operation.
Now the end/error tests have been moved to separate BIFs. The read and end/error tests are now two separate but related things.
You still had to test the value of the indicator in a separate line of code -- just as you have to check the BIF in a separate line of code. I don't see why the old indicator logic was "atomic" and the new one isn't. They work the same way!
However, the fact that you have to check the value in a separate line of code is the very problem that this thread was attempting to solve. By moving the %EOF check to a separate subprocedure, you've essentially put us back at square one.
Anyway, I don't think we're getting anywhere with this debate. We're clearly not going to agree on this, so there's little point in beating it to death. 

Particularly when this topic has been discussed so many times in the past.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.