Include version_enforcer.h
in all headers in CGAL
#7525
Replies: 6 comments 10 replies
-
Why not include it in |
Beta Was this translation helpful? Give feedback.
-
Can you please illustrate the first use case? The file uses a hard-coded version number that is checked against the CGAL version macros; if you put the file within CGAL, then the macro must have the version number, and then what is its purpose? |
Beta Was this translation helpful? Give feedback.
-
@MaelRL In the "normal" setup it is useless. @lrineau it sounds good... I'm wondering if it covers all our fork-cases |
Beta Was this translation helpful? Give feedback.
-
Jane's proposalLet me clear what I have understood. The goal of Jane is to enforce the same version in two files:
By default, without any user-specific modified headers, both would come from a distribution of CGAL, and would of course agree. With user-specific modified headers, a specific @janetournois: Is that a correct rephrasing of your idea, Jane ? Mael's proposalAnother proposal from Mael would be to encode the CGAL version in all CGAL headers, and make sure they can only be used in the right CGAL distribution. |
Beta Was this translation helpful? Give feedback.
-
@lrineau yes, exactly. It seems that Mael's proposal is another solution to the same problem. |
Beta Was this translation helpful? Give feedback.
-
Done in PR #7528 |
Beta Was this translation helpful? Give feedback.
-
@CGAL/geometryfactory what would you think about including the
version_enforcer.h
file to every header in CGAL, and adding the corresponding file to every release?It would sometimes help find inconsistencies between the versions that are used, in particular in specific projects development.
Then, in projects outside the repo, use a local
version_enforcer.h
, to make sure the user is using the right version of CGAL.Beta Was this translation helpful? Give feedback.
All reactions