× 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: %EOF
  • From: "Stone, Brad V (TC OASIS)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Fri, 18 Jun 1999 14:11:25 -0500

Dale,

First clue.  DOU vs. DOW.
Second clue.  Multiple exit points to a loop.  (Any comp sci book will tell
you this is a no-no)

Again, in the end it's simply a matter of preference.  Structure has nothing
to do with it.  I was simply pointing out a method that may solve the
problem, and including the gererally accepted method of using a priming
read.

Any more responses or anyone who wants to disagree, feel free but take it
off line.

Bradley V. Stone
BVS/Tools
http://www.bvstools.com




-----Original Message-----
From: Dan Bale [mailto:dbale@genfast.com]
Sent: Friday, June 18, 1999 1:00 PM
To: RPG400-L@midrange.com
Subject: RE: %EOF




Brad,

>>Key        SETLL    Filename
Key        READE    Filename

            DOW   not %EOF(Filename)

        (do some code here)
Key        READE    Filename
            Enddo

 Change it to this...  More structurally correct as well.<<

IMHO: No, no, no, no!!!!  How is that more "structurally correct" than:

Key      Setll     Filename
         DoU       %EoF
Key      ReadE     Filename
         If        not %EoF
.. do some code here ...
         EndIf
         EndDo

or maybe even:

Key      Setll     Filename
         DoU       %EoF
Key      ReadE     Filename
         If        %EoF
         Leave
         EndIf
.. do some code here ...
         EndDo

I would always rather have one READE in a loop than two.

Back to the original poster's question, though; it sounds like a bug.  Are
you
up to date on PTFs?  Might be worth checking.

- Dan Bale





* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  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.