Ivan Pribec

> Agreed. Using `gfortran` instead of `gnu` or `gcc` might be preferable for easy mapping between compiler executable name and profile, up to the moment someone is trying to compile...

On second thought, most compilers provide flags which allow to select fixed- or free-form format, meaning we could try and implement this without the need to rename files (e.g. if...

Good point. I recall now the [dbcsr](https://github.com/cp2k/dbcsr/) uses the `.F` extension for all their source files which are free-form. So we should agree on some sane default behavior and allow...

Here is a table of the respective compiler options for controlling input source format and preprocessing: | Compiler | Fixed-form | Free-form | Invoke (C) preprocessor | |----------|--------------|-------------|---------------------| | gfortran...

In the blog post from Steve, there is a link to a post from Intel: [Problem: Fortran source files not compiled when building in Visual Studio](https://software.intel.com/content/www/us/en/develop/articles/problem-fortran-source-files-not-compiled-when-building-in-visual-studio.html#add), which shows how the...

I agree that is cleaner. With respect to the preprocesser, I think we might need to distinguish between external preprocessors (like fypp, or [preform](https://github.com/szaghi/PreForM)) and those built into the compiler...

> > > Unless the names are treated differently I am a strong advocate for just ..f|.F|.F90|.f90. If specifying a suffix like .f03 meant Fortran was required to strictly apply...

> For a package that is intended to be designed for use by others I think I prefer the user being required to do the preprocessing themselves and only present...

The Rust [cc](https://crates.io/crates/cc) crate also has a [cc::Tool](https://docs.rs/cc/latest/cc/struct.Tool.html) class. The biggest difference is the compiler is configured via the `build.rs` build script. It makes sense that Fortran compiler integration must...

I've updated the table of options with more compilers (see original issue post). Here are the sources for each of them: * [nagfor](https://www.nag.com/nagware/np/r70_doc/nagfor.html#OPTIONS) * [SilverFrost FTN95](https://www.silverfrost.com/ftn95-help/options/quick_reference.aspx) * [Cray/HPE](https://support.hpe.com/hpesc/public/docDisplay?docId=a00115296en_us&page=Fortran_Command-line_Options.html) * [flang](https://reviews.llvm.org/D85363)...