You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tomasz-kaminski-sonarsource
changed the title
CPP-5655 Create rule S7119
CPP-5655 Create rule S7119: Global and static variables should not dependent on possibly uninitialized global variables
Oct 8, 2024
tomasz-kaminski-sonarsource
changed the title
CPP-5655 Create rule S7119: Global and static variables should not dependent on possibly uninitialized global variables
CPP-5655 Create rule S7119: Global and static variables should not dependent on possibly not yet initialized variables
Oct 8, 2024
loic-joly-sonarsource
changed the title
CPP-5655 Create rule S7119: Global and static variables should not dependent on possibly not yet initialized variables
Create rule S7119: Global and static variables should not dependent on possibly not yet initialized variables CPP-5655
Oct 9, 2024
The reason will be displayed to describe this comment to others. Learn more.
In the past, I used the Nifty counter idiom to solve initialization order issues. I'm not sure how relevant it is today, but it might be useful for legacy code? Should it be mentioned?
In the past, I used the Nifty counter idiom to solve initialization order issues. I'm not sure how relevant it is today, but it might be useful for legacy code? Should it be mentioned?
I think just having a function that returns a reference is a better and simpler solution in that case; see llvm::errs() vs std::cout. If you know good article about the Nifty counter, I think we could link it.
tomasz-kaminski-sonarsource
changed the title
Create rule S7119: Global and static variables should not dependent on possibly not yet initialized variables CPP-5655
Create rule S7119: Global should not depend on possibly not yet initialized variables CPP-5655
Oct 10, 2024
* Stack Overflow - Answer by Gabriel Staples for https://stackoverflow.com/a/73027793/24103368[What is the point of declaring "const volatile int *p"?]
* Stack Overflow - Answer by Gabriel les for https://stackoverflow.com/a/73027793/24103368[What is the point of declaring "const volatile int *p"?]
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
tomasz-kaminski-sonarsource
changed the title
loic-joly-sonarsource
changed the title
You can preview this rule here (updated a few minutes after each push).
Review
A dedicated reviewer checked the rule description successfully for: