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
tsaglam opened this issue
Dec 7, 2023
· 2 comments
Labels
bugIssue/PR that involves a buglanguagePR / Issue deals (partly) with new and/or existing languages for JPlagminorMinor issue/feature/contribution/change
I got errors while using cpp2 on C file
a quick test/analysis suggests that cpp2 assumes the code is C++ and that new is a keyword while it's not in C
more tests: cpp2 doesn't allow ÔŒλ and alike
The text was updated successfully, but these errors were encountered:
tsaglam
added
bug
Issue/PR that involves a bug
minor
Minor issue/feature/contribution/change
language
PR / Issue deals (partly) with new and/or existing languages for JPlag
labels
Dec 7, 2023
the C++ grammars-v4 targets C++14, the grammars-v4 repository also contains a grammar for C targeting C11, avoiding the new keyword issue
None support extended character (but \uXXXX are well supported). Reading the standard, it looks like those characters are implementation defined characters, and I suppose it's either a burden or not possible to have then in the a generic way in the grammar.
If jplag assumes a specific encoding for files, it may uses a patched version of the gramar to address the issue.
In an other hand, non ascii characters in identifier are far from common
bugIssue/PR that involves a buglanguagePR / Issue deals (partly) with new and/or existing languages for JPlagminorMinor issue/feature/contribution/change
From #1408:
The text was updated successfully, but these errors were encountered: