My issue is addressed to the principal OpenMC developers.
Is it allowed using existent third-party modules written in other compatible with GCC compilers languages, such as Fortran, in the C++ OpenMC core? I suppose that this is not desirable by default, but a case of significant improvement of the functionality and/or performance can be assumed.
Hi @vitmog and thanks for your question. The answer is no; every added dependency is added headache for the development team, and it’s hard enough just supporting C++ and Python as is.
How about using python module by first building your dynamic library by compiling your fortran code and making wrapping function based on C++ language? I have done this for coupling other code based on Fortran to OpenMC
Using a dynamic library requires producing additional non-standard code which is determined by at least the target OS, compiler, and target machine’s architecture. Consequently, it seems a much less preferable approach than the standardized C-Fortran binding where applicable. Thus, I doubt that it can be allowed by the OpenMC contribution policy.