-
Notifications
You must be signed in to change notification settings - Fork 1k
Allow indenting preprocessor macros? #1006
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
Comments
Why not. |
I had a look at the astyle docs, the indent-preproc-block option manages this. There seems to be no option to allow, but not require this indentation (but I think this is how astyle works with all options), so enabling this would mean a lot of files need to be updated (but again, astyle automates this). I just created #1007 to see what this would do. |
Hm, a related question: It seems that the github astyle check uses https://github.com/stm32duino/actions/tree/master/astyle-check which duplicates both the checking script as well as the astyle configs from the CI subdirectory in this repo. Why does the check not just run the script from this repo, so any changes to that are automatically applied? |
First goal is to have an action not dependent to the core. I did not find any "official" action for astyle that's why I've made my own one. |
Thanks @matthijskooijman |
While developing #997, I wrote some complicated and nested preprocessor statements. I originally tried making them clearer by applying indents, but that was not allowed by the astyle checks, so I removed them again. Now I wonder, should this astyle rule maybe be changed to allow (even if not require) indenting preprocessor directives?
e.g. consider:
vs:
The latter is IMHO a lot more readable.
The text was updated successfully, but these errors were encountered: