Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
New Contributor I
2 Views

Cant open MODULE file

I compiled this, but none of the other subroutines can open it.

It compiles with no errors.

I did notice that it gives an extension of .MOD, rather than

F90. Does that keep the other routines from using it ?

I could not upload the MOD file, apparently that is illegal.

Why does VS not allow this, when it compiles with no problem?

 

Can I force it to make an F90 file instead?

It wont upload the buildlog either.

0 Kudos
3 Replies
Highlighted
2 Views

Put the files in a ZIP and

Put the files in a ZIP and upload that.

If you have a module source (.f90) it will create a .mod file and also a .obj. The .mod will be automatically read when you say "USE modulename" in another Fortran source. Your source file should not be given a .mod file type.

Retired 12/31/2016
0 Kudos
Highlighted
New Contributor I
2 Views

OK, I got that, thanks !

OK, I got that, thanks !

I still am curious about something, though - - 

When I look at the solution space (Ctl-Alt-L) , I see 

"header files," and "resource files."

Does either of those have any relevance to a Fortran app?

0 Kudos
Highlighted
2 Views

Those "virtual folders" are

Those "virtual folders" are just for your convenience. They have no effect on the build process. When you add files to a project they may get sorted into those folders depending on the file type. Files recognized as resource files (.rc) go in Resource FIies and INCLUDE files (by default, .fd and .fi) go into Header Files. You are free to ignore those or add your own virtual folders.

Retired 12/31/2016
0 Kudos