Re: read on a do loop

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

> The stand alone ReadExample() is doing two things at once.

I disagree. It does one thing: it reads a record.  Whether or not some 
condition prevents that record from being read (error, lock, eof, etc) is 
a natural result of that one thing.

When you have the separate MoreRecords() subprocedure, you're doing one 
thing, but you've split it across two subprocedures -- which is exactly 
why you need to communicate the "end of file" condition from ReadExample() 
to MoreRecords() -- the reason they have to know about each other is 
because they're sharing a task.

Just my opinion, of course.