Hm. I thought it was pretty clear. I meant in PUBLIC statements. Like so:
module a
private
public :: sub1
contains
subroutine sub1()
...
end subroutine sub1
end module a
module b
use a
private
public :: sub1,sub2
contains
subroutine sub2()
end subroutine sub2
end module b
program main
use b
end program main
In some cases, if I wanted to access sub1 in program main, I had to have the
redeclaration of sub1 as public in module b. I would have thought I would
just have had to have
...
use a
...
and have sub1 come in. As I said, that was not always the case.
Alvaro Fernandez
-----Original Message-----
From: Fortran 90 List [mailto:[log in to unmask]]On Behalf
Of Richard Maine
Sent: Wednesday, July 16, 2003 5:26 PM
To: [log in to unmask]
Subject: Re: Modules USEing modules
Alvaro Fernandez writes:
> Some of the early Sun compilers did not reliably in my experience obey
this
> rule, so I was forced at times to redeclare subroutines even though they
> were ostensibly already in the scope. I wanted to verify that that was a
> compiler problem.
--
Richard Maine | Good judgment comes from experience;
[log in to unmask] | experience comes from bad judgment.
| -- Mark Twain
|