Support additional file extensions #250
Description
Once fpm will be out in the wild, we should try to support other Fortran file extensions.
This is not so important right now, but I thought I will create an issue since I gathered the information.
Here is a table of file extensions with default support by different compilers:
| Compiler | Fixed-form | Fixed-form with preprocessor | Free-form | Free form with preprocessor |
|---|---|---|---|---|
| gfortran | .f, .for, .ftn | .fpp, .F, .FOR, .FPP, .FTN | .f90, .f95, .f03, .f08 | .F90, .F95, .F03, .F08 |
| ifort | .f, .for, .ftn, .i | .fpp, .FPP, .F, .FOR, .FTN | .f90, .i90 | .F90 |
| nvfortran | .f .for .ftn | .F .FOR .FTN .fpp .FPP | .f90 .f95 .f03 | .F90 .F95 .F03 |
| nagfor | .f, .for, .ftn | .ff, .F | .f90, .f95 | .ff90, .ff95, .F90, .F95 |
| Cray | .f, .for | .F, .FOR | .f90, .f95, .f03, .f08, .f18, .ftn | .F90, .F95, .F03, .F08, .F18, .FTN |
| IBM | .f, .f77 | .F, .F77 | .f90, .f95, .f03, .f08 | .F90, .F95, .F03, .F08 |
| g95 | .f, .for | .F, .FOR | .f90, .f95, .f03 | .F90, .F95, .F03 |
The only options that are compatible along the tool-chains listed above are: .f, .F, .f90, .F90.
The .ftn extension has a clash between gfortran, ifort, and nagfor which assume fixed-form, and Cray which assumes free-form.
To enhance portability between compilers, we should either allow fpm to (copy and) rename the files silently, or have fpm print a message to the user to consider renaming his files.
Blog posts related to this issue:
Edit: Feel free to add more compilers.