# AStyle and JUCE coding style

**URL:** <https://forum.juce.com/t/astyle-and-juce-coding-style/13162>\
**Category:** Useful Tools and Components\
**Created:** [July 12, 2014, 6:27pm UTC](https://forum.juce.com/t/astyle-and-juce-coding-style/13162 "2014-07-12T18:27:09Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tadnicol](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/tadnicol/32/5141_2.png) [@tadnicol](https://forum.juce.com/u/tadnicol)\
**Post date:** [January 24, 2017, 7:23pm UTC](https://forum.juce.com/t/astyle-and-juce-coding-style/13162/2 "2017-01-24T19:23:05Z")

</div>

> [@Config for autoformatting following JUCE's coding standards](https://forum.juce.com/t/config-for-autoformatting-following-juces-coding-standards/17834):
>
> Hey, guys! I’ve created a config file for the AStyle (it’s very cool tool for file formatting and indentation). It includes almost all JUCE’s coding standards’ formatting rules. I think it could be convenient especially for the newcomers to JUCE. It’s very easy to use: astyle --options="juce\_astyle.options" [path to the file] If we want to perform recursive formatting we should use “-r” flag and wildcard: astyle --options="juce\_astyle.options" "\*.cpp" -r To perform a trial run with…

---

_[View the full topic](https://forum.juce.com/t/astyle-and-juce-coding-style/13162)._
