Hi

The sequence of the following modules is very important.
module A
end module A

module B
use A
end module B

If module B is put before module A then there will be compiled error:
Error: Error in opening the Library module file. [A]
I use CVF6.6c.

However, if I compiled it again, there will be no error.
It is a simple example.
When more module files use other module, things will be more complex.
I usually have to decide very carefully the sequence of the included
module files. Otherwise, there will be some unexpected error. I
found this today, after I arrange the sequence correctly. Some errors
are disappeared.

Mike wrote:
| Hi
|
| The sequence of the following modules is very important.
| module A
| end module A
|
| module B
| use A
| end module B
|
| If module B is put before module A then there will be compiled error:
| Error: Error in opening the Library module file. [A]
| I use CVF6.6c.
|
| However, if I compiled it again, there will be no error.
| It is a simple example.
| When more module files use other module, things will be more complex.
| I usually have to decide very carefully the sequence of the included
| module files. Otherwise, there will be some unexpected error. I ...

On Wed, 23 Apr 2008 01:03:32 -0700 (PDT), Mike gmail.com> wrote:

The standard says that a module must be "available" before you USE it. What
that means is not specified. For the compiler you're using, it means that
module A must have been compiled before a USE A can be processed. Since that
compiler processes program units sequentially in the source, if you put the
USE A earlier in the source file that defines module A, then you'll get this
error. On a recompile, module A was compiled previously so you don't see the
error, but if you changed module A you won't see the changes!

On Apr 23, 10:30 pm, Steve Lionel wrote:

Mike wrote:

If you're already creating separate files for the modules, then why on
earth would you then INCLUDE them in the main program file, instead of
just adding them to the project (where, typically, IJW)?

On Apr 24, 11:39 am, Craig Powers hal-pc.org> wrote:

I edit the IncludeAllModules.f90, which have:
include module_purposeA.f90
include module_purposeB.f90
...

On Wed, 23 Apr 2008 17:42:26 -0700 (PDT), Mike gmail.com> wrote:

[snip]

Yes,.

It depends on what you changed. In your case, you changed the executable code
only, so the object file that got created when module A was compiled a second
time got used in the subsequent link step.

In your example, module B doesn't actually use anything from module A. To see
what I was talking about, consider this version:

Mike wrote:

"Craig Powers" hal-pc.org> wrote in message
news:4811406e$0$9833$a726171b@news.hal-pc.org...

On Apr 25, 3:03 am, Steve Lionel wrote: