GeezerVison

While working on finalizing #448, I realized that astyle integration could be further improved to simplify the developer experience.

Once this is integrated, I suggest we also introduce a workflow running astyle

Cppcheck has moved to uncrustify quite a while ago, so simplecpp should probably do the same.

Thanks for the review.

so simplecpp should probably do the same.

Given limited bandwidth, I will not be able to switch to uncrustify. In the meantime, I think moving forward with this may be sensible as it allow contributor to apply the formatting.

I leave that up to @danmar.

Thanks for the taking the time to review 🙏

While I understand we could switch to uncrustify or clang-format, I think this is a sensible improvement to streamline contributions. The use of alternative formatters or linters could definitely be done in follow-up pull requests.

Once the GitHub workflow have been enabled and the test pass, I believe this will be ready for integration 🚀

cc: @danmar @firewave

Thank you for this contribution but I fear that I feel we should switch to uncrustify instead asap. If you don't have the bandwidth I understand. But we more or less just need to copy the runformat script from the cppcheck repo and reuse all the options..

Thanks for the feedback. I agree that moving to uncrustify makes sense long-term, and I understand the idea of reusing the runformat script from the cppcheck repo.

In the meantime, I believe these small changes still help streamline the contribution process for new contributors. To keep things clear and incremental, I’ll follow up with two pull requests:

• One with this commit: da16a44d (style: Format sources using astyle 3.0.1)
• One removing all remaining references to astyle, since the current instructions are outdated and misleading.

This way the repo stays consistent and contributors won’t be confused by stale formatting instructions while the switch to uncrustify is being worked out.