# Split between header and cpp in C++

**URL:** <https://forum.juce.com/t/split-between-header-and-cpp-in-c/46161>\
**Category:** General JUCE discussion\
**Created:** [May 24, 2021, 9:25am UTC](https://forum.juce.com/t/split-between-header-and-cpp-in-c/46161 "2021-05-24T09:25:44Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![aamf](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/aamf/32/19941_2.png) [@aamf](https://forum.juce.com/u/aamf)\
**Post date:** [May 25, 2021, 6:36am UTC](https://forum.juce.com/t/split-between-header-and-cpp-in-c/46161/11 "2021-05-25T06:36:26Z")

</div>

> [@Examples: Why is implementation code in header files?](https://forum.juce.com/t/examples-why-is-implementation-code-in-header-files/35043/8):
>
> FWIW thinking about how our SOUL codebase has ended up being structured (which is a good example at about 15 KLoC of extremely gnarly logic), a rough overview is: the nature of writing a compiler means you have a lot of classes, mostly small. And almost all the small classes (certainly anything under about 200LoC) are inline many bigger classes that are only used by a single piece of client code (i.e. are only included in a single .cpp file) are inline classes that are widely used across the w…

---

_[View the full topic](https://forum.juce.com/t/split-between-header-and-cpp-in-c/46161)._
