Re: Behavior when a do-iterator is changed

steve <kargls@xxxxxxxxxxx> wrote:

Your code is nonconforming. See my other post. The standard forbids
a program that causes a do-variable to become redefined or undefined
while the do-loop is active. Your program is clearly redefining the

It just occured to me that I am not sure of the requirements in
terms of not changing the value. Is:


allowed or not?

-- glen