Open richardpl opened 6 years ago
+1
+1
Preference for existing styleguide or (even better) linter?
FFmpeg is a good example indeed! (The only detail I don’t like is indent 4, because 2 is fully sufficient in my opinion.)
This is not only about tabs vs spaces. Currently QCTools uses mix of multiple naming conventions for functions/classes. Fixing all this looks like pretty big task. But after doing it right, code checker could probably be integrated into Travis to early notify about all the violations.
Fixing all this looks like pretty big task.
Indeed, yet a good code editor helps a lot.
As for the code conventions, I would suggest to follow the ones from Qt. I don't mind ffmpeg's ones but QCTools is Qt-based C++ application after all.
https://wiki.qt.io/Qt_Coding_Style https://wiki.qt.io/Coding_Conventions
No point in doing it manually if job can be automated.
I propose to run it under indent -kr -nut
to fix issues and also to remove trailing spaces and tabs.
+1 +1 +1
No point in doing it manually if job can be automated.
Of course not! I personally use BBEdit since years, which does this.
So, anything gonna happen anytime soon? Or I need to do it?
Be the change you want to see in the world, @richardpl
Can this be fixed at all?
Mixed tabs and spaces & mixed indentations are worst offenders.