From 07a2fe2f00122b514a5119b724581ea020d2c6ea Mon Sep 17 00:00:00 2001 From: "Michael Hirsch, Ph.D" Date: Tue, 12 Nov 2019 14:44:28 -0500 Subject: complete gfortran/intel/intel-cl fortran_std test --- docs/markdown/snippets/fortran_std.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 docs/markdown/snippets/fortran_std.md (limited to 'docs/markdown/snippets') diff --git a/docs/markdown/snippets/fortran_std.md b/docs/markdown/snippets/fortran_std.md new file mode 100644 index 0000000..2170a5e --- /dev/null +++ b/docs/markdown/snippets/fortran_std.md @@ -0,0 +1,14 @@ +## `fortran_std` option + +**new in 0.53.0** +Akin to the `c_std` and `cpp_std` options, the `fortran_std` option sets Fortran compilers to warn or error on non-Fortran standard code. +Only the Gfortran and Intel Fortran compilers have support for this option. +Other Fortran compilers ignore the `fortran_std` option. + +Supported values for `fortran_std` include: + +* `legacy` for non-conforming code--this is especially important for Gfortran, which by default errors on old non-compliant Fortran code +* `f95` for Fortran 95 compliant code. +* `f2003` for Fortran 2003 compliant code. +* `f2008` for Fortran 2008 compliant code. +* `f2018` for Fortran 2018 compliant code. \ No newline at end of file -- cgit v1.1