You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Fortran API triggers a bunch of warnings when compiled with gfortran and the -Wuse-without-only flag, e.g.:
...
Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only]
/home/stefano/Code/cp2k/tools/toolchain/install/trexio-2.4.2/include/trexio_f.f90:10889:20:
10889 | use, intrinsic :: iso_c_binding
| 1
Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only]
/home/stefano/Code/cp2k/tools/toolchain/install/trexio-2.4.2/include/trexio_f.f90:10899:20:
10899 | use, intrinsic :: iso_c_binding
| 1
Warning: USE statement at (1) has no ONLY qualifier [-Wuse-without-only]
/home/stefano/Code/cp2k/tools/toolchain/install/trexio-2.4.2/include/trexio_f.f90:10912:20:
...
It would be nice if the API file could be generated with the only keyword, specifying only the variables and procedures actually used from iso_c_binding.
The text was updated successfully, but these errors were encountered:
Noted! Do you think the use iso-c-binding call can be omitted in the basic Fortran function interfaces that have bind(C) in their declarations but which do not use any C native types or symbols like c_int32 or c_null_char?
Noted! Do you think the use iso-c-binding call can be omitted in the basic Fortran function interfaces that have bind(C) in their declarations but which do not use any C native types or symbols like c_int32 or c_null_char?
I don't think so because of the return type of the function which has to be a C type. Maybe subroutines without arguments will work, I need to try...
Currently, the Fortran API triggers a bunch of warnings when compiled with
gfortran
and the-Wuse-without-only
flag, e.g.:It would be nice if the API file could be generated with the
only
keyword, specifying only the variables and procedures actually used fromiso_c_binding
.The text was updated successfully, but these errors were encountered: