C code beautifier windows

JS Beautify , Pretty Diff. F90 ,. F95 ,. F03 ,. Fortran Beautifier. Gherkin formatter. Pug Beautify. Pretty Diff , JS Beautify. Latex Beautify. Lua beautifier. Remark , Prettier , Tidy Markdown. Marko Beautifier. Nginx Beautify. Rubocop , Ruby Beautify. TypeScript Formatter. TypeScript Formatter , Prettier.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 12 years, 8 months ago. Active 6 years, 8 months ago. Viewed k times. Active Oldest Votes. Styles can be inherited from a preset say LLVM or Google and can later override different options It is used by Google and others and is production ready.

We have some messy source files full of complicated macros, making it hard to understand how to modify the code or set breakpoints. We de-macroed it with gcc -E, resulting in very long lines of nested for loops, if statements etc. Astyle fixed that to be readable, saving us a lot of trouble. Astyle has a permanent place on my software toolshelf! This is a great tool. This can also be invoked using CTest:. There is also an install target, which can be used to install the Uncrustify executable typically make install.

An example of a single-configuration build system are Makefiles. You can build the Release configuration of Uncrustify from the build folder with:. Other build systems are multi-configuration, which means you specify the build type when building.

An example of a multi-configuration build system are Visual Studios project files. When you open the project in Visual Studio, you can select which configuration to build. You can also do this while building from the command line with cmake --build. Look at the Wiki. Look here. If you want to add a feature, fix a bug, or implement missing functionality, feel free to do so! Patches are welcome! Here are some areas that need attention:. Tested are the test cases, the formatting of the code base and the output of the command line options.

Every file ending with. Inside each line with these components is a single test: testNr[! Expected results have the following naming convention: testNr-testInputFileName. Optionally a! The codebase has to be formatted by the options set up in forUncrustifySources.

Failing to format the sources correctly will cause TravisCI build failures. If a PR is altering the CLI output, files inside those directories might need to be manually updated.

This often happens when options are added, removed or altered. Keep in mind that the version string line example: Uncrustify The p-file gives you details of the parsing process and indentation. The A-file gives you many details about the run itself, where the process is running thru, which values have the most important variables.

You can also dump the parsing information of each formatting step using the 'dump steps' option. You can combine this option with -p and -L to get a lot of detailed debugging information. It might be useful to add some code lines to see where something is happening. Remove the comment at line:. If you need a new option, there are a few steps to follow.

We are pretty sure that nothing OS-specific is used in the code base. The software has been previously tested on the following operating systems:. NOTE This application works reasonably well but it has bugs.

Do not apply it on your whole codebase without checking the results! The -c flag selects the configuration file. The -f flag specifies the input file. The -o flag specifies the output file. If flag -f is used without flag -o the output will be send to stdout.

Alternatively multiple or single files that should be processed can be specified at the command end without flags.