On 01/14/2015 11:02 AM, Thomas Ferris Nicolaisen wrote:
> On Wednesday, January 14, 2015 at 3:47:17 PM UTC+1, Peter van der Does
> wrote:
>     I don't know uncrustify, how can you tell with uncrustify if code is
>     not
>     in your preferred code style?
> There are a myriad of tools like this:
> http://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis
> They're basically some executable that run through a path of source
> files, parse them, do some analysis, and spit out a report that is
> either read by humans or used by some machine/script to notify the
> programmer that the code does not conform to their configured standards.

So how does uncrustify report back? Error codes, One liner, full report
in console, report in file etc etc etc.

Peter van der Does

GPG key: CB317D6E

Site: http://avirtualhome.com
GitHub: https://github.com/petervanderdoes
Twitter: @petervanderdoes

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to