Hi Alan.  Thanks again for the tip.  

I always grapple with the idea of not using iter and leave also.  I
don't see how it makes the code clearer to the reader, by eliminating
these ops.  I took your example, and eliminated the iter, as follows:


Dou iSay;
    iSay=*On;
   
    // Find next memo seq# for member
    SetGT(E)  (CI.Family#:CI.Member#) Mmemo_I;
    ReadPE(E) (CI.Family#:CI.Member#) Mmemo_I MI;
 
    If %Found(Mmemo_I);
       MO.Mmseq#=MI.Mmseq#+1;
    Else;
       MO.Mmseq#=1;
    EndIf;

    Monitor;
            Write Mmorec MO;

            On-Error *File;
               iSay=*Off;
    EndMon;
EndDo;

Now this is a very simple loop, and doesn't even transcend a page, but
in general, while perusing the code, you have to look to the beginning
of the loop to determine the condition of the loop.  If using iter,
you also have to peruse to the top of the loop anyways, so what's the
diff?


-- 
"Enter any 11-digit prime number to continue..."

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.