Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

got rid of global CTU::maxCtuDepth #6892

Merged
merged 1 commit into from
Oct 16, 2024
Merged

got rid of global CTU::maxCtuDepth #6892

merged 1 commit into from
Oct 16, 2024

Conversation

firewave
Copy link
Collaborator

No description provided.

@firewave firewave changed the title got rid of global CTU::maxCtuDepth [skip ci] got rid of global CTU::maxCtuDepth Oct 10, 2024
return Result::Fail;
if (temp > 10) {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to keep this cap for a few versions (with a deprecation) because users might have specified a higher value and removing it would lead to different behavior and possibly decreased performance.

That cap previously lived in the function findPath() in lib/ctu.cpp.

@firewave
Copy link
Collaborator Author

The initial changes exposes some currently horrible design with the checks having mSettings which might not be set. That is supposed to be started to be addressed with #5323.

@firewave
Copy link
Collaborator Author

I filed https://trac.cppcheck.net/ticket/13237 about removing this limitation.

@firewave firewave merged commit 56b7b6a into danmar:main Oct 16, 2024
66 checks passed
@firewave firewave deleted the ctu branch October 16, 2024 18:43
ludviggunne pushed a commit to ludviggunne/cppcheck that referenced this pull request Oct 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants