# Extending derived bind(c) types

**URL:** <https://fortran-lang.discourse.group/t/extending-derived-bind-c-types/6194>\
**Category:** Uncategorized\
**Created:** [July 21, 2023, 10:35am UTC](https://fortran-lang.discourse.group/t/extending-derived-bind-c-types/6194 "2023-07-21T10:35:21Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![FortranFan](https://avatars.discourse-cdn.com/v4/letter/f/96bed5/32.png) [@FortranFan](https://fortran-lang.discourse.group/u/FortranFan)\
**Post date:** [September 24, 2023, 4:30pm UTC](https://fortran-lang.discourse.group/t/extending-derived-bind-c-types/6194/18 "2023-09-24T16:30:35Z")

</div>

> [@LocalSimplicity](#):
>
> … I want to explore portability, performance and usability of certain C++ abstraction layers (e.g., Kokkos, Sycl) together with the existing Fortran code base…

@LocalSimplicity ,

That is a tall order.

Chances are you can achieve one goal, possibly usability - see a silly example [**here**](https://fortran-lang.discourse.group/t/return-an-array-of-strings-from-fortran-to-c/5100/7) as just some food for thought!

But that might fall short of the other two; or, at best, get two of your goals, perhaps performance also with some processors and companion processors e.g., Intel +LLVM. However that may not yield true portability.

---

_[View the full topic](https://fortran-lang.discourse.group/t/extending-derived-bind-c-types/6194)._