× 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.



I agree with what Eric said.
John Brandt
iStudio400.com
(903) 523-0708

-----Original Message-----
From: DeLong, Eric [mailto:EDeLong@xxxxxxxxxxxxxxx]
Sent: Friday, November 21, 2003 9:09 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Two reade loops: which one preferred ?


In addition, I find the priming read to be extremely useful if you are
incorporating level break logic, as it allows you to initialize the break
values before you enter the loop.  I can't tell you how much I hate to see
level break logic muddied up by initialization code.  


Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Jon Paris [mailto:Jon.Paris@xxxxxxxxxxxxxx]
Sent: Friday, November 21, 2003 8:03 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Two reade loops: which one preferred ?


 >> So, applying the C/PASCAL approach to RPG forces to include one
additional read before the loop as in Style#1.

I always code the additional read before the loop - but for very
straightforward logical reasons that have nothing to do with choice of
language.

If the very first read of a file causes EOF, then that (in most cases) will
be an _error_ condition.  On the other hand, EOF within the loop is an
_expected_ condition - or I'll never get out!

I simply prefer to handle those widely different circumstances with two
separate reads.

Jon Paris
Partner400
www.Partner400.com


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.542 / Virus Database: 336 - Release Date: 11/18/03
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.542 / Virus Database: 336 - Release Date: 11/18/03
 

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.