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

code reorg #32

Open
rfvander opened this issue Mar 31, 2017 · 3 comments
Open

code reorg #32

rfvander opened this issue Mar 31, 2017 · 3 comments
Labels
enhancement

Comments

@rfvander
Copy link
Contributor

  • Source files are gradually getting out of hand in terms of size. We need to break them into pieces and give them recognizable names

  • Source and header files are currently mixed. all header files should go to the include directory

  • We need to clean up stray text, decide on a uniform coding and commenting style
@keitat
Copy link
Contributor

keitat commented Mar 31, 2017

Any suggestions? As for headers, I do not see any in src except the one auto-generated by .in file.

@rfvander
Copy link
Contributor Author

It was a general comment. It will take some time to develop a uniform coding style. Of course, if you already have one, we can adopt that.

Yes, can we move that generated header file to /include as well?

@keitat
Copy link
Contributor

keitat commented Apr 1, 2017

Yes, I can. I guess we also want to make the best effort to keep 1-to-1 correspondence between .h and .c files.

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

No branches or pull requests
2 participants
@rfvander @keitat