Ivan Pribec

I mean if you would run a hypothetical `$ fpm --export-cps` and it created the binary artefacts (archive, `.mod`) files and `package.cps` file, the artefacts are specific to the particular...

I suppose this could fall under a subcase of non-portability related to generic interface (https://github.com/klausler/fortran-wringer-tests/tree/main?tab=readme-ov-file#generic-interfaces). In this example the combination of keyword arguments and types is needed to complete the...

I guess I don't have access to those two that think it's always present. But I like the interpretation of the two that get it right. :)

I've been pointed to the fact, the program is actually illegal, due to Section 15.5.1, paragraph 2, > The data-ref in a procedure-designator shall not be an unallocated allocatable variable...

That is also how I envisioned it. If the order is changed to: ``` allocate(f) call f%check allocate(foo :: g) call g%check ``` the compilers I have access to work...

Short answer is you need to change it in the `config.toml`: ``` [markup.highlight] style = "catppuccin-latte" ```

That configures correctly, but `nagfor` doesn't recognize the same flags. We would need to add use generator expressions in the `target_compile_options` command. ``` [ 55%] Building Fortran object tests/CMakeFiles/test_attr.dir/test_attr.F90.o make[2]:...

At least for the first scenario, I believe in Cargo it is done using environment variables. Quoting the relevant sections: > Cargo exposes these environment variables to your crate when...

The main benefit I see is you don't have to install a dozen `.mod` files, but just `mpi_f08.mod` and `libvapaa.a`. Nice and clean.

SIMD directives are part of the standard since OpenMP 4.0. By default options like `-fopenmp`/`-qopenmp` will also turn on the SIMD directives. The reason there are separate flags is if...