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

rename zassert functions #21783

Closed
andrewboie opened this issue Jan 9, 2020 · 2 comments
Closed

rename zassert functions #21783

andrewboie opened this issue Jan 9, 2020 · 2 comments
Labels
Enhancement Changes/Updates/Additions to existing features

Comments

@andrewboie
Copy link
Contributor

Coverity thinks any function with the word "assert" in its name is a conditionally compiled expression, and generates false positives about side effects.

To avoid this hassle, rename the zassert... family of APIs used in our test cases to something which doesn't have "assert" in the same. zcheck perhaps?

The existing APIs should be marked with __deprecated and just call the new APIs. All test cases should be converted.

@andrewboie andrewboie added the Enhancement Changes/Updates/Additions to existing features label Jan 9, 2020
@jukkar
Copy link
Member

jukkar commented Jan 17, 2020

I am not familiar with Coverity so do not know if this is possible, but IMHO we should instead try to configure Coverity to not generate these false positives. It sounds wrong to change our code just to satisfy some weird rule in a tool.

@nashif
Copy link
Member

nashif commented May 28, 2021

agree with @jukkar

@nashif nashif closed this as completed May 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Changes/Updates/Additions to existing features
Projects
None yet
Development

No branches or pull requests

3 participants