Re:Show HN: A 2D game engine in under 1000 lines of C
by flukus on Sunday February 02, 2020 @10:20PM
(#22221164)
The question should probably be what you gain from the header files? If you just want the simplicity you can "#include \"some_file.c\"" instead. Functionally it's no different, but it's less surprising to other people and it's an easier transition to a real build system if/when you need it. I think the reason it's being raised is because people think your writing a header only library.
[ Parent
| on HN ]
Re:Show HN: A 2D game engine in under 1000 lines of C
by ryanpcmcquen on Monday February 03, 2020 @02:08AM
(#22222062)
In my experience, including `"some_file.h"` is more common than `"some_file.c"`. I also like knowing at a quick glance what the entry point/main file is. That's less explicit when all the files have the same extension.