Defining the struct in the header file doesn't actually do anything but define the contract that users of the struct will follow.

As I'm spending some time back in the land of low-level C, I'm trying to fully get my head around best-practices for header files and code organization, so I thought I'd toss out some questions ...

Zapccs parses C++ header files just once and keeps in memory both all template instantations and generated code.