diff --git a/docs/LibASTMatchersTutorial.rst b/docs/LibASTMatchersTutorial.rst index 13749fbc41..1e88ec203c 100644 --- a/docs/LibASTMatchersTutorial.rst +++ b/docs/LibASTMatchersTutorial.rst @@ -153,7 +153,7 @@ documentation `_. CommonOptionsParser OptionsParser(argc, argv, MyToolCategory); ClangTool Tool(OptionsParser.getCompilations(), OptionsParser.getSourcePathList()); - return Tool.run(newFrontendActionFactory()); + return Tool.run(newFrontendActionFactory().get()); } And that's it! You can compile our new tool by running ninja from the @@ -299,7 +299,7 @@ And change ``main()`` to: MatchFinder Finder; Finder.addMatcher(LoopMatcher, &Printer); - return Tool.run(newFrontendActionFactory(&Finder)); + return Tool.run(newFrontendActionFactory(&Finder).get()); } Now, you should be able to recompile and run the code to discover for diff --git a/docs/LibTooling.rst b/docs/LibTooling.rst index 57f207f275..75ef6a0fe7 100644 --- a/docs/LibTooling.rst +++ b/docs/LibTooling.rst @@ -99,7 +99,7 @@ our ``FrontendAction`` over some code. For example, to run the // on. Thus, it takes a FrontendActionFactory as parameter. To create a // FrontendActionFactory from a given FrontendAction type, we call // newFrontendActionFactory(). - int result = Tool.run(newFrontendActionFactory()); + int result = Tool.run(newFrontendActionFactory().get()); Putting it together --- the first tool ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -136,7 +136,7 @@ version of this example tool is also checked into the clang tree at CommonOptionsParser OptionsParser(argc, argv, MyToolCategory); ClangTool Tool(OptionsParser.getCompilations(), OptionsParser.getSourcePathList()); - return Tool.run(newFrontendActionFactory()); + return Tool.run(newFrontendActionFactory().get()); } Running the tool on some code