Re: infinite loop

I use infinate loops in one instance, and one instance only.

my subfile processing template program looks something like this (psuedocode)

-----
begsr

exsr inzsfl
exsr loadpage

dow 1=1
exfmt screen

select
when cmd3
exsr endpgm
leave

when cmd12
leave

when cmd4
exsr prompt
iter

when pagedown
exsr loadpage
iter

other
exsr edit

if errors
iter
end

exsr update
leave
endsl

enddo

endsr
----

because sometimes of so many different reasons to iter or leave, I
don't want my loop dependent on some nebulous variable that I have to
declare, set and change depending on how I want the loop to behave.

adding command keys or functions is simple - just another when section
- very predictable behavior.

iterate or leave.  no worries, no hassles, no ambiguity, no errors no
declaring variables.

jmho.


On 9/14/06, Booth Martin <booth@xxxxxxxxxxxx> wrote:

I happen to like "dou 'dog' = 'cat' because it immediately tells the
programmer something infinite is happening here.

However, in my experience, an infinite loop usually means a broken
thought process.  There is a need for infinite loops, but not very
often, in my opinion.

*ducking*

rob@xxxxxxxxx wrote:
> If you notice, they refer you to FOR.  You might try
> for x = 1 to *hival;
> but you'd have to define x and then I'd wonder what about internal
> precision, etc.  For example, if x was defined as 1,0, what happens when x
> goes over 9?
>
>
> Rob Berendt

--
-----------------------------
Booth Martin
www.martinvt.com
-----------------------------
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.