Ivan Pribec

I can't see any benefit in allowing redundant stuff. In my eyes it just causes confusion; there are some redundant operators in [fpm](https://github.com/fortran-lang/fpm) modules.

I find this pattern used often in "beginner" programs, e.g. ```fortran radius = str2real(input("Enter a radius: ")) print *, "Area of circle: ", radius*pi**2 end ``` But like you suggest...

I think `stdlib_io` is a suitable place for it. On Mon, 7 Dec 2020 at 15:57, Jeremie Vandenplas wrote: > I agree with others: I think input() would be a...

The application was creating Fortran interfaces from the C prototypes. The current script iterates over the parameter list and creates Fortran interface blocks such as: ```fortran interface subroutine bli_?setijv(ar,ai,i,x,incx) real(c_double),...

In that case I'd just note that `void*` also appears in the prototypes for `??copysc`, `??cast[m|v]`, `??castnzm`, `?fprint[m|v]` and `?print[m|v]`.

I can confirm the bug with, ``` > git clone https://github.com/scivision/ffilesystem.git > fpm build --link-flag "-lm -lstdc++" --cxx-compiler g++-14 --verbose ... ar: creating archive build/gfortran_FA0A528919A6C0C3/ffilesystem/libffilesystem.a [ 96%] libffilesystem.a done. [...

Also seems to be a duplicate of https://github.com/fortran-lang/fpm/issues/811

You are referring to the issue also documented here, https://cyber.dabamos.de/programming/modernfortran/preprocessor.html, > As CPP, the preprocessor of GNU Fortran, is not indicating the current operating system, we have to pass the...

Just to add my two cents on modules and doing the "wrapping" in Fortran. The main benefit would be eliminating issues with different calling conventions and name mangling, which differ...

According to [this issue](https://gitlab.com/x86-psABIs/x86-64-ABI/-/issues/4) on the x86-64-ABI repo, in practice the hidden length argument is of type `size_t`: > At least Intel Fortran, GNU Fortran (GFortran), and LLVM flang all...