Replies: 4 comments 1 reply
-
Not helpful, but I ran into this issue today. I think an easy fix in fast-dds-gen would be to use the '#pragma once' instead in the headers for guards. |
Beta Was this translation helpful? Give feedback.
-
Found this issue after submitting a PR. Agreed that #pragma once might be cleaner provided it is available on supported compilers. |
Beta Was this translation helpful? Give feedback.
-
Labeling this ticket as enhancement and moving it to the Ideas discussion forum where enhancements and feature requests are discussed. |
Beta Was this translation helpful? Give feedback.
-
With our code generator we add a hash to the include guard, see for example https://github.com/RemedyIT/idl2cpp11/blob/de2b1cd7ab5951cc856179a9030297c2c5e8806d/examples/const/testC.h#L9 |
Beta Was this translation helpful? Give feedback.
-
We have two IDLs with the same name but different namespaces:
e.g.
one_project/a_folder/SomeThing.idl
one_project/b_folder/SomeThing.idl
Using the FastDDSGen tool we have seen that the generated code is actually creating matching include guards because the include guards are just based on the file name.
Can this be patched to generate the include guards using the folder the IDL is in or some additional information to distinguish between two IDLs with matching names and different contents?
Beta Was this translation helpful? Give feedback.
All reactions