summaryrefslogtreecommitdiffstats
path: root/clang-tools-extra/test/clang-tidy/cppcoreguidelines-owning-memory-legacy-functions.cpp
diff options
context:
space:
mode:
authorHaojian Wu <hokein@google.com>2017-10-18 15:56:39 +0000
committerHaojian Wu <hokein@google.com>2017-10-18 15:56:39 +0000
commit9e0f7f1a23b5c2d11e4efc8b9113080c31605768 (patch)
tree91356735d2677d94b28565053be6ef62b6bbc766 /clang-tools-extra/test/clang-tidy/cppcoreguidelines-owning-memory-legacy-functions.cpp
parent3de36d6f11a75eba93f855f24660ef93405ac150 (diff)
downloadbcm5719-llvm-9e0f7f1a23b5c2d11e4efc8b9113080c31605768.tar.gz
bcm5719-llvm-9e0f7f1a23b5c2d11e4efc8b9113080c31605768.zip
Support Objective-C/C++ source files in check_clang_tidy.py
check_clang_tidy.py currently only handles C and C++ source files. This extends the logic to also handle Objective-C (.m) and Objective-C++ (.mm) files. However, by default, clang compiles .m/.mm files using Objective-C 1.0 syntax. Objective-C 2.0 has been the default in Xcode for about 10 years, and Objective-C Automatic Reference Counting (ARC) for about 6 years, so this enables both by default. (Clients which actually want to test clang-tidy checks for Objective-C 1.0 or non-ARC files can pass custom flags to check_clang_tidy.py after --, which will disable the Objective-C 2.0 and ARC flags). I did not add logic to handle running clang-tidy on Objective-C header files alone; they also use the .h file extension, so we'd need to look inside their contents. I included a new test to confirm the new behavior. Depends On D38963 Patch by Ben Hamilton! llvm-svn: 316090
Diffstat (limited to 'clang-tools-extra/test/clang-tidy/cppcoreguidelines-owning-memory-legacy-functions.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud