[llvm-bugs] [Bug 47067] New: automatically recognise the same file extensions as gcc does

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=47067

            Bug ID: 47067
           Summary: automatically recognise the same file extensions as
                    gcc does
           Product: clang
           Version: trunk
          Hardware: All
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: Frontend
          Assignee: unassignedclangbugs at nondot.org
          Reporter: dapaixaocaio at gmail.com
                CC: llvm-bugs at lists.llvm.org, neeilans at live.com,
                    richard-llvm at metafoo.co.uk

clang is supposed to be -- and it mostly is -- compatible with gcc, but it
still doesn't recognises all file extensions gcc does out of the box. sure, it
obviously recognises common extensions like `*.c`, `*.cpp`, `*.h`, and `*.hpp`,
but not some less known file extensions like `.h++` and `.hp`, which gcc does.
i think clang should, in order to have better compatibility/parity with gcc.

here's all file extensions gcc recognises but clang doesn't:
* .hh
* .HH
* .hp
* .HPP
* .h++
* .sx
* .tcc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200810/87078095/attachment.html>