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


  • Subject: RE: READE is confusing to me
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Wed, 13 Sep 2000 09:21:09 -0700

It's a semantic thing, but it took me a while to realize what %found,
%equal, and %eof are intended to mean.  Fortunately, I found out where I was
wrong before I installed the programs that used them incorrectly.  I had to
read the manuals very carefully.  Some people may find them intuitive

> -----Original Message-----
> From: M. Lazarus [mailto:mlazarus@ttec.com]
> Sent: Monday, September 11, 2000 8:45 PM
> To: RPG400-L@midrange.com
> Subject: RE: READE is confusing to me
> 
> 
> At 9/11/00 08:05 AM -0400, you wrote:
> >%Equal is used on Setll or Lookup
> 
>   I think that the implementation of these BIFs makes them 
> inconsistent.  Even though there was considerable thought 
> behind it, I 
> think it ended up being misguided.  I think that they s/b 
> consistent for 
> ALL I/O opcodes.  This means that all CHAIN's and READx's should have 
> %Found and %EOF available.
> 
>   Does anyone else find the implementation confusing?
> 
>   -mark
> 
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.