|
Jeez, I guess I'll never learn... (donning asbestos suit - again): Sorry I missed this on your original post. Too busy pontificating on the functional rather than the philosophical <g>. Although, on second glance, I think it was Booth's endorsement on this point that got me going. > The other rule of thumb I try to stick to is to have read loops no longer than > can comfortably be seen on one SEU screen. If I have more processing > than can be done 'between the reads', I typically move it into a subroutine. And, so, now you have to go find that subroutine in another place in the source, which is _still_ more than one screenful. Finding the matching EndDo is, potentially, only more of a problem (than finding the EndSr) if it's not documented (as I mentioned in my previous post, 'tis my practice to do this). Unless the 'between the reads' code is repeated somewhere else in the program, I usually avoid moving it to a subroutine. I still use subroutines to break up large sections of code into functional pieces, but the read loop structure does not drive that decision. Uh oh, I feel a rant mode coming on... (RANT MODE: ON) It drives me crazy to to have to jump around in subroutines nested ten or more levels deep. And the three statement subroutines? What are these geniuses thinking of? (RANT MODE: OFF) Hey, forgive me. It's Monday _AND_ it's tax day; I was up waaaaaaaaaaaay too late finishing my taxes last night. So, this will be my last post today. (We'll see about that!) - Dan Bale > -----Original Message----- > From: boothm@earth.Goddard.edu [SMTP:boothm@earth.Goddard.edu] > Sent: Sunday, April 16, 2000 11:33 AM > To: RPG400-L@midrange.com > Subject: RE: RPG Indicators > > Now there's a sensible rule! I sure wish it was a standard in the > community. > > _______________________ > Booth Martin > boothm@earth.goddard.edu > http://www.spy.net/~booth > _______________________ > > > > > "Rich Duzenbury" <rduz@westernmidrange.com> > Sent by: owner-rpg400-l@midrange.com > 04/16/2000 12:06 AM > Please respond to RPG400-L > > > To: <RPG400-L@midrange.com> > cc: > Subject: RE: RPG Indicators > > > OH BOY. > > The other rule of thumb I try to stick to is to have read loops no longer > than can comfortably be seen on one SEU screen. If I have more processing > > than can be done 'between the reads', I typically move it into a > subroutine. > > Regards, > Rich +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.