Re: best way to use the USE statement
- From: nospam@xxxxxxxxxxxxx (Richard E Maine)
- Date: Wed, 30 Aug 2006 14:51:44 -0700
Kamaraju Kusumanchi <kk288@xxxxxxxxxxx> wrote:
[Is it better to put USE statements at the module level or in eachprocedure]
This has been discussed here before, and I recall different people
having different viewpoints on the matter. I don't think there is a
universally accepted "best" way. I don't recall that I convinced
everyone that my preferences were best, and I'm sure that the opposing
camp didn't convince me of theirs. I think that all you can do is
consider the issues and then decide for yourself which way best works
for you.
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.
--
Richard Maine | Good judgment comes from experience;
email: my first.last at org.domain| experience comes from bad judgment.
org: nasa, domain: gov | -- Mark Twain
.
- Follow-Ups:
- Re: best way to use the USE statement
- From: James Giles
- Re: best way to use the USE statement
- References:
- best way to use the USE statement
- From: Kamaraju Kusumanchi
- best way to use the USE statement
- Prev by Date: best way to use the USE statement
- Next by Date: Fortran for new and old Macs on OS X
- Previous by thread: best way to use the USE statement
- Next by thread: Re: best way to use the USE statement
- Index(es):
Relevant Pages
|