In article <ron-shepard-9B8689.19535201062012@news60.forteinc.com>, Ron
Shepard <ron-shepard@NOSPAM.comcast.net> writes:

> I also don't see exactly what the problem is. From what I can
> understand from the previous posts, something like the following
> seems like an obvious and straightforward solution:

Yes, this will work and is functionally the same. See my reply from
today to Richard Maine.

> The idea of making local variables in one routine visible to another
> routine seems really bad to me. For many reasons. The the main one
> is that it would allow a local variable to just magically change
> value in the middle of an execution sequence with no clue to the
> programmer what might be happening. That's not supposed to happen,
> no way no how.

If one were using a module variable visible to more than one routine,
this could also happen. Moreover, ANY routine in which it is visible
could change it. ALLOW alerts the programmer and compiler to this
possibility.