Re: automated coding style tool

Phi via Gdb
2025-01-17T17:36:16Z

On 17/01/2025 16:55, Simon Marchi via Gdb wrote:

>
> Of course, like Joel said, ill-formatted code will certainly get
> committed at some point, but the nightly job will tell us. It's a quick

Just curious about this interesting thread. I'd like to understand the ill-formatted concept while using a code formatter. I was wondering a !ill-formatted, i.e a well-formatted should always produce a no diff output on its input, I mean

$ format-tool foo.c

must produce foo.c with no diff's, a hook of some kind can be implemented may be at commit or push time (or git-send-mail) saying the format-tool must be run first and QA re-run.

I jumped into this trail, so may this has been discussed already.

Cheers.