× 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.



Hi Bob -

EVERY programmer, without exception, that I've seen code this type
of stuff, assumes that READ and READE return a %FOUND() condition
rather than %EOF(). %EOF may be important, but %FOUND is how we
logically think it should be coded.

I sure hope Hans & Barbara get a chance to "enhance" this in V5.3
and also get to PTF it back to V3R2.  (Just kidding about the PTF
thing).

While I agree that it would have been really, really, really nice if READ/READE/READP/READPE had been implemented to set %FOUND, I don't think it can be changed now because it would break programs that use a %FOUND condition from a CHAIN/SETLL/LOOKUP after some intervening READxx operation.


I don't do that, I eval the %FOUND status into a named indicator if I'm going to use it other than right after the operation that set it, but there are probably people that do, and those programs would stop working correctly.

Ken
http://www.ke9nr.net/
Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.