Re: Array Constructors

Jan Vorbrüggen wrote:
|| 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.

Let me pile on Jan's questions: if it was decided that implied DO-loop variables
were different (IMO reasonably), why weren't they simply dismissed from
the "scope" of IMPLICIT NONE? (IOW, they could be left undeclared and
integer-by-default). I still have to put "INTEGER, PRIVATE:: k" at the top
of my modules whenever I use k in an implied-DO of an initialization statement.

--
Jugoslav
___________
www.xeffort.com

Please reply to the newsgroup.
You can find my real e-mail on my home page above.

.

Quantcast