You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current definition for C++ headers looks like this:
"extensions":[
"hh",
"hpp",
"hxx",
"inl",
"ipp"
]
However, this incorrectly identifies C++ header files as C, as seen with this front-end program:
What this is missing from the above definition is .h, which is commonly used for both C and C++. Detecting which is which may be a little bit tricky. I suggest inspecting the code of GitHub Linguist to see how it detects this (as it does so properly).
To test if it works or not, you can test on Godot. It should show up as about 94.4% C++ code.
The text was updated successfully, but these errors were encountered:
@aaronfranke Thank you for your issue! This is at least some what of a duplicate of #67. So I'm going to close this issue in favour of that. I will say that these kinds of "mistakes" are quite intentional as I don't like the idea of language detection being something that is obfuscated or nondeterministic.
However there is definitely more language detection methods on the table that are quite deterministic (like modeline) that I do want to add to tokei, and for the rest of the cases I want to provide easy configuration so that you the user gets what they expect.
The current definition for C++ headers looks like this:
However, this incorrectly identifies C++ header files as C, as seen with this front-end program:
What this is missing from the above definition is
.h
, which is commonly used for both C and C++. Detecting which is which may be a little bit tricky. I suggest inspecting the code of GitHub Linguist to see how it detects this (as it does so properly).To test if it works or not, you can test on Godot. It should show up as about 94.4% C++ code.
The text was updated successfully, but these errors were encountered: