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

Coding style and static analysis #112

Open
ArcEye opened this issue Aug 3, 2018 · 1 comment
Open

Coding style and static analysis #112

ArcEye opened this issue Aug 3, 2018 · 1 comment
Labels
Cross-Stacks Issue Issue relevant to both HAL and CNC stack enhancement

Comments

@ArcEye
Copy link
Contributor

ArcEye commented Aug 3, 2018

Issue by machinekoder
Tue Dec 2 10:10:02 2014
Originally opened as machinekit/machinekit#391


We should enforce a specific coding style for every language in the project. This can e.g. be done by using astyle. My code editor (Kate) always shows mixed indentations (tabs and spaces) everywhere. This makes the code unreadable on some platforms and is possible error source.

Furthermore every piece of code that is commit should be checked with suitable static code analysis tool. For C and C++ cppcheck and clang might be suitable. For Python pep8 is the way to go. This ensures that common error will not make its way into the project.

@ArcEye
Copy link
Contributor Author

ArcEye commented Aug 3, 2018

See machinekit/machinekit-cnc#38 for full text, this is a copy header only.

@ArcEye ArcEye added the Cross-Stacks Issue Issue relevant to both HAL and CNC stack label Aug 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Cross-Stacks Issue Issue relevant to both HAL and CNC stack enhancement
Projects
None yet
Development

No branches or pull requests

1 participant