|
midrange.com
ReadExample();
DoW MoreRecords();
If Condition;
Iter; // Oooops! the loop will never end
EndIf;
ReadExample();
EndDo;
What does this buy you? You could've just coded:
read myfile;
dow not %eof(myfile);
if condition;
// do something.
endif;
read myfile;
enddo;
The entire point behind moving the READ into a subprocedure was so that it
could be used as the control point for the loop. Having a separate
MoreRecords() subprocedure completely defeats the purpose.
Furthermore, it introduces the ITER problem that you've pointed out -- which wasn't a problem when the loop was being controled by a read that was on the DOW statement.
Plus, you've introduced a need for communication between the ReadExample() and MoreRecords() subprocedures. Now ReadExample() has to tell MoreRecords() when there are more records to be read. That means that you either need to pass a cookie between the two, or that you need to use oft-shunned global variables.
What was wrong with the original design?
dow ReadExample();
// do something
enddo;
As an Amazon Associate we earn from qualifying purchases.
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.
