4 ms·
Keeping .c and .h files separate is pointless, *.c and *.h can pick them out when necessary. 'include' is a good choice for libraries, the external interface, b
by veltas 3y ago
Keeping .c and .h files separate is pointless, *.c and *.h can pick them out when necessary. 'include' is a good choice for libraries, the external interface, but not necessary for internal headers.
- actionfromafar 3y agoIf you have a bunch of platform specific code it can be quite neat to have .c and .h files separately. Then each platform gets its own directory with .c files.
- masfoobar 3y agoWhen I build C projects which, admittedly, is making a game, I always start off with platform specific code. This is very handy by splitting up .h and .c files. ie... platform.h platform_windows.c platform_linux.c etc. This way, my build file for windows uses platform_windows.c, etcetc.