Proposed coding style for C, Linux++ #209
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The intention of this is to serve as a help/guidance for both devs and reviewers of pull requests.
Baseline is taken from Linux v6.5.6, with some (possibly) controversial additions (at the end of the file):
I've also added a couple of exceptions for macros like
TAILQ_FOREACH()
which are used as control statements (if, while, for), so the opening brace should be on the same line -- otherwise clang-format thinks we are creating a recursive function ... 🙄This PR also contains a set of small fixes/cleanup to confd and statd.
Emacs Users <3
Emacs users may want to set up
format-all
withuse-package
, it supports all common formatters. For some guidance, see https://ianyepan.github.io/posts/format-all/. Here's what I use myself:Wnich can be simplified to:
If you for some reason do not have
use-package
set up already, here's a quickie: