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.

Sign up for GitHub

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

Jump to bottom

perform static analysis #5

Open
bruceravel opened this issue Jun 20, 2014 · 2 comments
Open

perform static analysis #5

bruceravel opened this issue Jun 20, 2014 · 2 comments

Comments

@bruceravel
Copy link
Contributor

Matt suggested

 It would be nice to come up with a tree of called functions and 
 dependencies -- I think  there are quite a few completely unused 
 functions, and lots of commented out code blocks.   These should
 all be removed - they exist in the initial git commit, so are not
 lost to history, but there's no reason to have to look at that.
@bruceravel
Copy link
Contributor Author

Just made a PR containing static analysis, including call trees, for the whole code base. No problems get solved, but it's a start.

@bruceravel
Copy link
Contributor Author

In #19 everything has been subjected to memory analysis using Valgrind.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bruceravel