The use of "user_config.h"

[kolban]

I'm starting to think that the "user_config.h" might not be a great idea. It seems that in a number of SDK supplied headers, they try and include a C include file called "user_config.h" which is not supplied with the SDK but is, instead, expected to be supplied by the application programmer. What I am not seeing is why this pattern is present? Why not omit any inclusion of "user_config.h" and simply let the programmer include it (or not) as needed in their own apps? I keep finding myself creating an empty "user_config.h" just for the purpose of satisfying the compiler ... and when I do that, warning bells start to go off. It can mean I don't understand something properly ...

What does the community think about the "user_config.h" mandatory header file?

[eriksl]

It's one of the things that needs improvement. Just like the pile of functions that lack a prototype, that's very basic stuff missing!

[dkinzer]

I keep finding myself creating an empty "user_config.h" just for the purpose of satisfying the compiler [...]

Although purists might object, I created the empty user_config.h in the SDK include directory.