owenca wrote:

> > I think it should be opt in. See [#191295 
> > (comment)](https://github.com/llvm/llvm-project/issues/191295#issuecomment-4228702589).
> 
> I disagree, that should work out of the box and there isn't any harm here. 
> The extensions are currently mapped to C++. I don't think there are e.g. 
> `foo.java.in` files which are currently formatted as C++ and afterwards they 
> would be formatted as Java.
> 
> Files like `config.h.in` or similar are quite common, and it should "just 
> work", when they need to be parsed as C instead of C++.
> 
> A command line option is cumbersome, especially if you just want to use e.g. 
> `git clang-format`.

Good point. Anyway, it seems that this patch wouldn't interfere with the 
command-line option I suggested.

https://github.com/llvm/llvm-project/pull/191502
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to