# Weather and climate modeling codes from Fortran to C++

**URL:** <https://fortran-lang.discourse.group/t/weather-and-climate-modeling-codes-from-fortran-to-c/1531>\
**Category:** Uncategorized\
**Created:** [July 9, 2021, 2:30am UTC](https://fortran-lang.discourse.group/t/weather-and-climate-modeling-codes-from-fortran-to-c/1531 "2021-07-09T02:30:55Z")\
**Posts on this page:** 1\
**Showing post:** 46

<div class="post-metadata">

**Author:** ![FedericoPerini](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/federicoperini/32/1750_2.png) [@FedericoPerini](https://fortran-lang.discourse.group/u/FedericoPerini)\
**Post date:** [March 26, 2024, 5:57pm UTC](https://fortran-lang.discourse.group/t/weather-and-climate-modeling-codes-from-fortran-to-c/1531/46 "2024-03-26T17:57:13Z")

</div>

It will be impossible to make everybody happy, but we’ve been discussing interfaces at length with @jeremie.vandenplas, @everythingfunctional, @hkvzjal, @gnikit et al. during our past Monthly calls.

So far we’ve come up with some interesting things:

- All procedures that could be made `pure` were made `pure` (first time ever?)

- Generalised `KIND`-dependent functions and 128-bit linear algebra support (first time ever?)

- 2/3 interfaces for each operation, ideally:

We also do not want to deviate too much from common interfaces such as NumPy and SciPy, because that’s what most people are used to nowadays.

See for example the current matrix inversion interface:

> <https://github.com/perazz/fortran-lapack/blob/869e12f0aff09e3520a828e11e90898591872d47/src/stdlib_linalg_inverse.f90#L11-L16>

Of course all comments and ideas are very welcome and we’ll do our best to optimize across all the requests!

---

_[View the full topic](https://fortran-lang.discourse.group/t/weather-and-climate-modeling-codes-from-fortran-to-c/1531)._