There are conditions in which it's a perfectly good approach.
One example; an outer while loop processes and validates the front panel
control settings for a process that is to run repetitively in the inner
while loop. The inner loop continues until a change is detected on the front
panel, in which case it exits, the outer loop processes the new settings
and, if "stop" is not pressed, restarts the inner loop. Perfectly acceptable
in my view for simpler programs that don't really warrant a state machine.
alberto wrote in message
news:506500000005000000F7230000-986697009000@quiq.com...
> Just a question: why do you have two while loop nested and running at
> the same time, this in general is not a good approach unless the
> inside loop is a sub-v
i that is executed at condition; in fact the
> inside loop takes all the control when running and the outside loop
> waits for the inside loop to stop before doing another loop. If you
> want to stop them at the same time there's no need for the outside
> loop to exist.