# About inheritance and abstract types

**URL:** <https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801>\
**Category:** New to Julia\
**Tags:** inheritance\
**Created:** [September 9, 2017, 5:28pm UTC](https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801 "2017-09-09T17:28:13Z")\
**Posts on this page:** 1\
**Showing post:** 27

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [June 12, 2020, 12:38pm UTC](https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801/27 "2020-06-12T12:38:43Z")

</div>

> [@williamfgc](#):
>
> Julia essentially implements the Fortran model

I am not sure I understand what “the Fortran model” is in this context.

> [@williamfgc](#):
>
> Their choice is to organize using OO architecture.

Again, I don’t understand the what the issue is. It is possible to provide idiomatic interfaces in Julia to external libraries that are organized using OO. There are many examples.

> [@williamfgc](#):
>
> the mentioned alternatives mean that get\_type must be implemented in all derived types

This is not true. Perhaps you missed @mauro3’s [answer](https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801/12).

---

_[View the full topic](https://discourse.julialang.org/t/about-inheritance-and-abstract-types/5801)._