maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

Normalized the usage of override in the doc. 

llvm-svn: 202710
This commit is contained in:
Alexander Kornienko 2014-03-03 13:36:30 +00:00
parent 5ea34fcc8d
commit 7c9b29f525
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
clang-tools-extra/docs/clang-tidy.rst
View File

@ -215,8 +215,8 @@ In this case we need to override two methods:
...
class ExplicitConstructorCheck : public ClangTidyCheck {
public:
void registerMatchers(ast_matchers::MatchFinder *Finder);
void check(ast_matchers::MatchFinder::MatchResult &Result);
void registerMatchers(ast_matchers::MatchFinder *Finder) override;
void check(ast_matchers::MatchFinder::MatchResult &Result) override;
};
In the ``registerMatchers`` method we create an AST Matcher (see `AST Matchers`_
@ -259,8 +259,7 @@ The check should be registered in the corresponding module with a distinct name:
class MyModule : public ClangTidyModule {
public:
virtual void
addCheckFactories(ClangTidyCheckFactories &CheckFactories) override {
void addCheckFactories(ClangTidyCheckFactories &CheckFactories) override {
CheckFactories.addCheckFactory(
"my-explicit-constructor",
new ClangTidyCheckFactory<ExplicitConstructorCheck>());