Re: best way to use the USE statement
- From: "James Giles" <jamesgiles@xxxxxxxxxxxxxxxx>
- Date: Thu, 31 Aug 2006 00:36:00 GMT
Richard E Maine wrote:
....
For what it is worth, I'm in the camp of putting all the USE
statements at the top of the module. My main reason is that I
consider it to be part of the high-level information to know what
other modules this one might have dependencies on. I find that more
important than knowing which modules each subroutine depends on.
After all, I have to compile the module as a whole - not each
subroutine separately.
But several people whose judgement I respect are in the other camp.
I'd agree with you *if* I could control host association. As it
is, there are cases where one is more legible, and there are cases
where the other is.
--
J. Giles
"I conclude that there are two ways of constructing a software
design: One way is to make it so simple that there are obviously
no deficiencies and the other way is to make it so complicated
that there are no obvious deficiencies." -- C. A. R. Hoare
.
- Follow-Ups:
- Re: best way to use the USE statement
- From: Ron Shepard
- Re: best way to use the USE statement
- References:
- best way to use the USE statement
- From: Kamaraju Kusumanchi
- Re: best way to use the USE statement
- From: Richard E Maine
- best way to use the USE statement
- Prev by Date: Re: closing unit=5 and unit=6 and print *
- Next by Date: Scope of implied-do index
- Previous by thread: Re: best way to use the USE statement
- Next by thread: Re: best way to use the USE statement
- Index(es):
Relevant Pages
|