Make include guards unique

[elfring]

:thought_balloon: I find that an include guard like “VINA_H” is too short for the safe reuse of your header file (when it belongs to an application programming interface).

[diogomart]

Thanks. Do you know of an actual conflict or is it just to prevent a possible conflict?

[elfring]

:thought_balloon: I propose to reduce the probability for undesirable naming conflicts another bit.

:crystal_ball: Will the collaboration with C++ modules become more attractive accordingly?

[diogomart]

Sounds like it might be a good idea.

Is backwards compatibility a concern?

[elfring]

:crystal_ball: Would you prefer an other name pattern than appending a kind of UUID?