# Is ISO\_Fortran\_binding.h compatible for different Fortran ABIs?

**URL:** https://fortran-lang.discourse.group/t/is-iso-fortran-binding-h-compatible-for-different-fortran-abis/2652
**Category:** Help
**Created:** [January 25, 2022, 10:35am UTC](https://fortran-lang.discourse.group/t/is-iso-fortran-binding-h-compatible-for-different-fortran-abis/2652 "2022-01-25T10:35:50Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)
#### Post date: [January 25, 2022, 3:51pm UTC](https://fortran-lang.discourse.group/t/is-iso-fortran-binding-h-compatible-for-different-fortran-abis/2652/4 "2022-01-25T15:51:44Z")

</div>

> [@aradi](#):
>
> But if you wish to look at the bright side of it, it is absolutely consistent with, how it currently works (or to be more precises, how it currently does not work) between Fortran components compiled with different Fortran compilers. Why should the C/Fortran interface be easier to handle than the Fortran/Fortran interface.

Too bad, at least for me this makes the ISO\_Fortran\_binding.h look like a step back when interfacing to C. For module files Fortran compilers usually choke on modules produced by other vendors, yet a C compiler will happily compile against any ISO\_Fortran\_binding.h found somewhere in the include path and maybe horribly fail at runtime. There are a few macros around which could help detect this on the C side, however those won’t be available on the Fortran side.

---

_[View the full topic](https://fortran-lang.discourse.group/t/is-iso-fortran-binding-h-compatible-for-different-fortran-abis/2652)._