diff options
| author | Jussi Pakkanen <jpakkane@gmail.com> | 2019-03-14 23:37:50 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-03-14 23:37:50 +0200 |
| commit | 2b446ab53978d18898eca5661e9752bc75b0a794 (patch) | |
| tree | 0b0bba8baadf9b04bed36540a7126b005564abc8 /docs/markdown | |
| parent | 1f0b3652ac0abd15a8212a4cf9f3d9d5c4579c98 (diff) | |
| parent | e491792a956dfae50cfae90cad7b7b6732b74c3d (diff) | |
| download | meson-2b446ab53978d18898eca5661e9752bc75b0a794.zip meson-2b446ab53978d18898eca5661e9752bc75b0a794.tar.gz meson-2b446ab53978d18898eca5661e9752bc75b0a794.tar.bz2 | |
Merge pull request #5081 from scivision/fortraninclude
FEATURE: Fortran Include directive
Diffstat (limited to 'docs/markdown')
| -rw-r--r-- | docs/markdown/snippets/fortran-include.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/markdown/snippets/fortran-include.md b/docs/markdown/snippets/fortran-include.md new file mode 100644 index 0000000..a811765 --- /dev/null +++ b/docs/markdown/snippets/fortran-include.md @@ -0,0 +1,12 @@ +## Fortran `include` statements recursively parsed + +While non-standard and generally not recommended, some legacy Fortran programs use `include` directives to inject code inline. +Since v0.51, Meson can handle Fortran `include` directives recursively. + +DO NOT list `include` files as sources for a target, as in general their syntax is not correct as a standalone target. +In general `include` files are meant to be injected inline as if they were copy and pasted into the source file. + +`include` was never standard and was superceded by Fortran 90 `module`. + +The `include` file is only recognized by Meson if it has a Fortran file suffix, such as `.f` `.F` `.f90` `.F90` or similar. +This is to avoid deeply nested scanning of large external legacy C libraries that only interface to Fortran by `include biglib.h` or similar. |