RE: Standards question: What is your feeling about %found & %eof vs. %found(file) & %eof(file) ?

I once had to maintain a program that had > 50 layers of nesting; mostly IF's. It was before the days of /free so it was pretty darned difficult to determine which END (didn't even use ENDIF/ENDDO, etc.) went with which construct. I wonder how WDSc's "Convert to /free" option would tackle that? I mean, the indentation would have just rolled off the right edge of the screen!

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Wednesday, July 02, 2008 12:21 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Standards question: What is your feeling about %found & %eof vs. %found(file) & %eof(file) ?

I try to avoid that these days. Between compound IF statements and the
use of subroutines and/or subprocedures, I try to avoid more than four
layers of nesting. It's not always possible, but it's something I
strive for. I mean, unless you have one line per state, you're talking
about many dozens of lines of code when you nest ten deep. I prefer to
try and limit my procedures to a single visible page (about 40-50
lines). I realize that's an arbitrary limit and it could technically
allow much deeper indentation, but again, I do my best to avoid it.

Joe