Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I would like to change all code to *.F90 and be able to use pre-processor in fortran code too. #214

Closed
edwardhartnett opened this issue Jan 31, 2020 · 3 comments · Fixed by #366

Comments

@edwardhartnett
Copy link
Contributor

In olden times there was no distinction between .f90 and .F90 files. But these days, .F90 is preferred and there is a distinction.

The distinction is that all fortran compilers will now run .F90 files through the pre-processor. This is the new normal for Fortran.

We don't use the pre-processor in our fortran code, but we should follow the convention of using .F90. Some of our files are F90 and some f90. We can change the .f90 to .F90 and be consistent and in conformance with modern fortran practice.

@ArchangeGabriel
Copy link
Contributor

In my understanding, the good practice is that .F90 should only be used when the file must go through the pre-processor, while .f90 should be used otherwise.

@edwardhartnett
Copy link
Contributor Author

Well that's true and I was waiting for an example before I reply, but I would like all Fortran code to go through the pre-processor, including test codes, so that's why I want to switch to .F90. ;-)

For an example of why see #254

GFDL and NOAA now distribute a lot or all of their fortran code as .F90, and count on the pre-processor, and that seems to work OK. All the Fortran compilers support that these days.

@edwardhartnett edwardhartnett changed the title we have some *.f90 and some *.F90, all should be *.F90 I would like to change all code to *.F90 and be able to use pre-processor in fortran code too. May 7, 2020
@edwardhartnett
Copy link
Contributor Author

See #355 for further discussion...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants