RE: CHAIN Versus SETLL and READ When Data Needed

Our company standard is an infinite loop:

Setll keyfield File1;
Dow 1 = 1;
   Reade keyfield File1;
   If %Eof(File1);
      Leave;
   Endif;
   // valid record read - do something
Enddo;

This was our way of making loops consistant, and not having to worry about
if the the programmer decided to put the read at the top of the loop, or at
the bottom, or both - since some of the old code has really long and if you
couldn't find the enddo, you could miss something.
Carmen Nuland 

-----Original Message-----
From: Booth Martin [mailto:booth@xxxxxxxxxxxx] 
Sent: Thursday, March 01, 2007 8:10 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: CHAIN Versus SETLL and READ When Data Needed

Is that a good practice?  I can't imagine a design need for an endless loop?

Wes Reinhold wrote:

There was a lot of 'bad mouthing' of iter, leave, etc. yesterday.  How 
would you get out of a DOW 0=0 without using them?