summaryrefslogtreecommitdiff
path: root/docs/markdown/snippets/fortran_std.md
diff options
context:
space:
mode:
authorJussi Pakkanen <jpakkane@gmail.com>2020-01-07 19:32:34 +0200
committerJussi Pakkanen <jpakkane@gmail.com>2020-01-07 22:12:25 +0200
commit8d576eba9190f311e845f08ce822972b34c4e973 (patch)
treed7add41a3b2d463f89be86577f3ba8503663f521 /docs/markdown/snippets/fortran_std.md
parenta1d2444e4aac7df1a7f5d36246f64ea0564d38a4 (diff)
downloadmeson-8d576eba9190f311e845f08ce822972b34c4e973.tar.gz
Prepare new release.0.53.0
Diffstat (limited to 'docs/markdown/snippets/fortran_std.md')
-rw-r--r--docs/markdown/snippets/fortran_std.md14
1 files changed, 0 insertions, 14 deletions
diff --git a/docs/markdown/snippets/fortran_std.md b/docs/markdown/snippets/fortran_std.md
deleted file mode 100644
index 2170a5eb6..000000000
--- a/docs/markdown/snippets/fortran_std.md
+++ /dev/null
@@ -1,14 +0,0 @@
-## `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