Uh oh!
There was an error while loading. Please reload this page.
cleaned up access of the check classes - #5387
Conversation
firewave
commented
Sep 1, 2023
This highlights that (outside of testing) most of the implementations of the check do not need to be visible at all outside of their TU. This is what triggered me to start #5323. |
There was a problem hiding this comment.
Well I agree it would be ideal to encapsulate the check classes better in the normal cppcheck program. However I do not feel sure about this. friend is really ugly. There is the expression: "In C++, your friend can see your privates".
I see no ideal solution that people will not see problems with.
firewave
commented
Sep 1, 2023
The |
Yeah I know, that is your intention. Any class that happens to have a certain name can see those privates, you don't technically enforce somehow that this is only used in testing. I don't feel excited about adding friends. And well I don't feel totally excited about alternatives neither. |
firewave
commented
Sep 2, 2023
Before it was The code should not have |
danmar
commented
Sep 4, 2023
we can delay this refactoring until after the release at least. |
firewave
commented
Sep 4, 2023
Fine with me. |
danmar
commented
Sep 11, 2023
well.. all I say is that I don't know any solution that I like. Let's do it this way if you think this is better. |
firewave
commented
Sep 11, 2023
You're gonna like #5435. 😃 |
No description provided.