Disambiguate headers

[benedekkupper]

There are two major problems with this project's header style, that should be addressed:

Header file extensions

Most embedded projects use a mix of C and C++ language code. In this environment it is very misleading to use .h for C++ headers that the C compiler cannot compile. Having a clear separation (using .h for C and .hpp for C++ headers) makes detecting wrong includes immediately visible and easy to troubleshoot.

Furthermore, the generated header files should also adopt this, preferably with .pb.hpp extension, as the .pb is a canonical semi-extension that commonly refers to protobuf generated output.

Header file scope

Having very generic header names such as Defines.h, Errors.h gives a high chance of header name collision with the application it is integrated into. The headers should either be prefixed with the project name, or moved into a subdirectory and included with the directory name, e.g. #include "EmbeddedProto_Defines.hpp" or #include "EmbeddedProto/Defines.hpp".

[BartHertog]

Hello @benedekkupper,

Thanks again for your feedback on Embedded Proto and for helping us improve it!

With regard to the generated headers and their extensions:
When reviewing one of your other tickets, I noticed you changed the extension in your branch. I understand your point. I think selecting the output extension in a config file That would allow for backwards compatibility while moving forward. I will look into how this would work. I am open to alternatives.

With regard to header file scope:
For some time now, I have considered implementing a single header (EmbeddedProto.h) that includes all the other headers. This will reduce the chance of name collisions. There is a disadvantage to this: you will include everything at all times, including headers you do not need.