# Workaround for traditional inheritance features in object-oriented languages

**URL:** <https://discourse.julialang.org/t/workaround-for-traditional-inheritance-features-in-object-oriented-languages/1195>\
**Category:** General Usage\
**Tags:** inheritance, structtypes\
**Created:** [December 29, 2016, 2:25am UTC](https://discourse.julialang.org/t/workaround-for-traditional-inheritance-features-in-object-oriented-languages/1195 "2016-12-29T02:25:45Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![tshort](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tshort/32/43_2.png) [@tshort](https://discourse.julialang.org/u/tshort)\
**Post date:** [January 6, 2017, 6:20pm UTC](https://discourse.julialang.org/t/workaround-for-traditional-inheritance-features-in-object-oriented-languages/1195/29 "2017-01-06T18:20:17Z")

</div>

This is really getting to be a FAQ. Here’s another approach by Mike Innes with his `@forward` macro that helps with the bookkeeping of your option #2.

- [Is there a Julian way to combine types generically or a design pattern that achieves the goal? - #9 by MikeInnes](https://discourse.julialang.org/t/is-there-a-julian-way-to-combine-types-generically-or-a-design-pattern-that-achieves-the-goal/983/9)
- [http://mikeinnes.github.io/2016/03/21/sorting.html](http://mikeinnes.github.io/2016/03/21/sorting.html)

---

_[View the full topic](https://discourse.julialang.org/t/workaround-for-traditional-inheritance-features-in-object-oriented-languages/1195)._