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

The Monolithic Static Analysis Thread #1

Open
flibitijibibo opened this issue Dec 21, 2015 · 2 comments
Open

The Monolithic Static Analysis Thread #1

flibitijibibo opened this issue Dec 21, 2015 · 2 comments
Labels

Comments

@flibitijibibo
Copy link
Member

flibitijibibo commented Dec 21, 2015

This will act as the monolithic thread for bringing our static analysis warnings down to 0, for ALL possible analyzers. For starters, here are our current reports:

VS 2017: http://fna.flibitijibibo.com/analyze2017.txt

The Utilities/ folder is the only folder that is NOT to be touched. This is because we need to keep MonoGame compatibility for these files in particular. In addition, we will NOT be touching the StockEffects since those came directly from Microsoft, so changing them would only be more inaccurate. Lastly, these reports include messages for third-party libs; you ignore these warnings.

For this task, simply take any task in the report you want (letting us know you're doing so), send me the PR to fix it, and I'll update the report.

Ideally we should be able to properly fix all of these defects, but some are by XNA4's design... for example, Microsoft.Xna.Framework.Input.Touch is a massive namespace, and Gendarme reports this, but we can't change this without breaking XNA4 compatibility. In these situations, add a line to suppress the warning and document why the suppression is needed.

As we get closer to resolving all the warnings I'll be lowering the threshold for warning level and certainty, so expect more defects to show up as the list gets smaller.

If you decide to take a task, please post here and let us know you're working on it. Because we're doing so much work on so much code, we need to be sure we're not conflicting with other branches.

@flibitijibibo
Copy link
Member Author

This has been updated with a VS2017 report for the new FAudio rewrite.

@flibitijibibo
Copy link
Member Author

I think it's time to revive this... in particular we should be able to replace this thread with GitHub Actions. I would really like to add a C# /analyze action to FNA, and Clang static analysis actions for FAudio and FNA3D (probably not Theorafile since it's mostly Xiph code that we're never going to change). If anyone likes working with Actions and wants to write this in, I'll take it in and we can close this for good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant