Re: Array Constructors
- From: Jan Vorbrüggen <jvorbrueggen@xxxxxxxxxxxxxxx>
- Date: Wed, 28 Feb 2007 18:09:18 +0100
Also note that I/O-implied DO variables are different. They do not have
their own scope, but are "ordinary" variables. There was once a time
when I was unaware of this distinction myself (and thus made a fool of
myself vehemently explaining something that turned out to be wrong. Oh
well. It happens).
Is there any good reason for this, apart from "this is how the vote went" (if anybody ever noticed before it was too late" or "we put it in so that Richard Maine would have a chance to make a fool of himself" 8-)? I can't see a technical need for two of the implied-do-variable types to behave one way and the third in another.
Jan
.
- Follow-Ups:
- Re: Array Constructors
- From: glen herrmannsfeldt
- Re: Array Constructors
- From: Jugoslav Dujic
- Re: Array Constructors
- From: Richard Maine
- Re: Array Constructors
- References:
- Array Constructors
- From: cjk32
- Re: Array Constructors
- From: Michael Metcalf
- Re: Array Constructors
- From: cjk32
- Re: Array Constructors
- From: *** Hendrickson
- Re: Array Constructors
- From: Richard Maine
- Re: Array Constructors
- From: Richard Maine
- Array Constructors
- Prev by Date: Re: optional argument versus subroutine overloading
- Next by Date: Re: Array Constructors
- Previous by thread: Re: Array Constructors
- Next by thread: Re: Array Constructors
- Index(es):