Feature or enhancement
Proposal:
While I was implementing #119976, I observed that some macros are not guarded against possible constructions because their content is only wrapped in {} but not in the classical do { ... } while(0) construction.
For instance, the current VISIT macro sometimes requires the semi-colon and sometimes not depending on how it is used, which I find a bit confusing. I think it's preferrable to always require to add the ;.
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Linked PRs
Feature or enhancement
Proposal:
While I was implementing #119976, I observed that some macros are not guarded against possible constructions because their content is only wrapped in
{}but not in the classicaldo { ... } while(0)construction.For instance, the current
VISITmacro sometimes requires the semi-colon and sometimes not depending on how it is used, which I find a bit confusing. I think it's preferrable to always require to add the;.Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Linked PRs