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

Tracking where problems/features happen #19

Open

oulrich1 opened this issue Feb 8, 2012 · 0 comments

Labels

Member

oulrich1 commented Feb 8, 2012

The code needs to be commented with descriptions of where type declarations are made (there are some such as "SEE SETTINGS.h but not enough).

Modules that have a problem/bug/added-feature need to have a description of the problem/addition and how it effects other parts.

Also, each file needs a description of what it does in relation to the program from a user's perspective. Or at least a description of what it does.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment