Ive, 2 months ago

@peturdainn de resultaten zijn duidelijk, er is maar 1 goeie manier!

peturdainn, 2 months ago

@Ive inderdaad... ik zal me moeten aanpassen

ives, 2 months ago

@peturdainn In the header file. But make sure you use include guards in your header files.
https://en.wikipedia.org/wiki/Include_guard

peturdainn, 2 months ago

@ives yeah I know

and I agree with doing it in the header file for things that can be thought of a components.

For own code, I'm leaning towards putting it in source, because opening the c file shows me a list of other files that the code depends on.

And that's even more so when you get headers included in headers and again included in headers

ives, 2 months ago

@peturdainn I wouldn't do that. For complex projects, that list in the source file can get rather long. And what do you do if a header changes and no longer depends on another one? Do you edit all the files that include it to remove the include there as well? Sounds quite bothersome.

peturdainn, 2 months ago

@ives I tend to group functionality in components or API's so changes in them have no effect, but yes sometimes the list gets long

OTOH the discussion started here because somebody had been doing something in a separate part of the code not quite by the (design) book and caused weirdness, and without the headers in headers I would never have seen their non-conforming constructs