.c files compile to .obj files, which are linked together after compilation (by the linker) into the executable (or library), so there is no need to include one .c file in another
For me that means that there are two ways to use this library, a shared object (.so) file or a number of header files.
I feel like there's less need for a .so file and using a bunch of headers will be easier to use in embedded devices.
I think it's better to move all the parts of midi-message-parser to header files, based on the structs. Related branch.
According to this StackOverflow answer,
For me that means that there are two ways to use this library, a
shared object(.so) file or a number of header files.I feel like there's less need for a
.sofile and using a bunch of headers will be easier to use in embedded devices.List of
ifndefstatements:#ifndef LOGGING_DISABLED#ifndef MIDI_H__#ifndef NULLTO-DO:
ifndefsections, make sure header version works the same way as C-file versionUPD: I think it'll be ok if I clarify the previous library uses doing a PR.