My philosophy is to use the ".F90" extension only and add the following at the beginning of every single Fortran file:
#if defined HAVE_CONFIG_H
#include "config.h"
#endif
This makes it much easier then to write makefiles (only one extension for all source files) and track dependencies automatically (scripts are easier to write and understand, with less if's). When a previously non-preprocessed Fortran file starts to include preprocessing options, there is no need to change anything in the build system. All this has a positive impact on developers, in particular on newcomers, who need as much clarity and straightforwardness as possible.
However I don't want to enforce any practice. If you prefer to selectively preprocess Fortran files, I'll follow your specifications.
My philosophy is to use the ".F90" extension only and add the following at the beginning of every single Fortran file:
#if defined HAVE_CONFIG_H
#include "config.h"
#endif
This makes it much easier then to write makefiles (only one extension for all source files) and track dependencies automatically (scripts are easier to write and understand, with less if's). When a previously non-preprocessed Fortran file starts to include preprocessing options, there is no need to change anything in the build system. All this has a positive impact on developers, in particular on newcomers, who need as much clarity and straightforwardness as possible.
However I don't want to enforce any practice. If you prefer to selectively preprocess Fortran files, I'll follow your specifications.