Documentation: random cleanups. Use monospaced font where appropriate,
highlight console output with "code-block:: console", etc.
llvm-svn: 170276
diff --git a/clang/docs/ClangPlugins.rst b/clang/docs/ClangPlugins.rst
index cf53817..7c5c65c 100644
--- a/clang/docs/ClangPlugins.rst
+++ b/clang/docs/ClangPlugins.rst
@@ -2,56 +2,56 @@
Clang Plugins
=============
-Clang Plugins make it possible to run extra user defined actions during
-a compilation. This document will provide a basic walkthrough of how to
-write and run a Clang Plugin.
+Clang Plugins make it possible to run extra user defined actions during a
+compilation. This document will provide a basic walkthrough of how to write and
+run a Clang Plugin.
Introduction
============
Clang Plugins run FrontendActions over code. See the :doc:`FrontendAction
-tutorial <RAVFrontendAction>` on how to write a FrontendAction
-using the RecursiveASTVisitor. In this tutorial, we'll demonstrate how
-to write a simple clang plugin.
+tutorial <RAVFrontendAction>` on how to write a ``FrontendAction`` using the
+``RecursiveASTVisitor``. In this tutorial, we'll demonstrate how to write a
+simple clang plugin.
-Writing a PluginASTAction
-=========================
+Writing a ``PluginASTAction``
+=============================
-The main difference from writing normal FrontendActions is that you can
-handle plugin command line options. The PluginASTAction base class
-declares a ParseArgs method which you have to implement in your plugin.
+The main difference from writing normal ``FrontendActions`` is that you can
+handle plugin command line options. The ``PluginASTAction`` base class declares
+a ``ParseArgs`` method which you have to implement in your plugin.
-::
+.. code-block:: c++
- bool ParseArgs(const CompilerInstance &CI,
- const std::vector<std::string>& args) {
- for (unsigned i = 0, e = args.size(); i != e; ++i) {
- if (args[i] == "-some-arg") {
- // Handle the command line argument.
- }
- }
- return true;
+ bool ParseArgs(const CompilerInstance &CI,
+ const std::vector<std::string>& args) {
+ for (unsigned i = 0, e = args.size(); i != e; ++i) {
+ if (args[i] == "-some-arg") {
+ // Handle the command line argument.
}
+ }
+ return true;
+ }
Registering a plugin
====================
A plugin is loaded from a dynamic library at runtime by the compiler. To
-register a plugin in a library, use FrontendPluginRegistry::Add:
+register a plugin in a library, use ``FrontendPluginRegistry::Add<>``:
-::
+.. code-block:: c++
- static FrontendPluginRegistry::Add<MyPlugin> X("my-plugin-name", "my plugin description");
+ static FrontendPluginRegistry::Add<MyPlugin> X("my-plugin-name", "my plugin description");
Putting it all together
=======================
-Let's look at an example plugin that prints top-level function names.
-This example is also checked into the clang repository; please also take
-a look at the latest `checked in version of
-PrintFunctionNames.cpp <http://llvm.org/viewvc/llvm-project/cfe/trunk/examples/PrintFunctionNames/PrintFunctionNames.cpp?view=markup>`_.
+Let's look at an example plugin that prints top-level function names. This
+example is also checked into the clang repository; please also take a look at
+the latest `checked in version of PrintFunctionNames.cpp
+<http://llvm.org/viewvc/llvm-project/cfe/trunk/examples/PrintFunctionNames/PrintFunctionNames.cpp?view=markup>`_.
-::
+.. code-block:: c++
#include "clang/Frontend/FrontendPluginRegistry.h"
#include "clang/AST/ASTConsumer.h"
@@ -114,31 +114,31 @@
Running the plugin
==================
-To run a plugin, the dynamic library containing the plugin registry must
-be loaded via the -load command line option. This will load all plugins
-that are registered, and you can select the plugins to run by specifying
-the -plugin option. Additional parameters for the plugins can be passed
-with -plugin-arg-<plugin-name>.
+To run a plugin, the dynamic library containing the plugin registry must be
+loaded via the :option:`-load` command line option. This will load all plugins
+that are registered, and you can select the plugins to run by specifying the
+:option:`-plugin` option. Additional parameters for the plugins can be passed with
+:option:`-plugin-arg-<plugin-name>`.
Note that those options must reach clang's cc1 process. There are two
ways to do so:
-- Directly call the parsing process by using the -cc1 option; this has
- the downside of not configuring the default header search paths, so
- you'll need to specify the full system path configuration on the
- command line.
-- Use clang as usual, but prefix all arguments to the cc1 process with
- -Xclang.
+* Directly call the parsing process by using the :option:`-cc1` option; this
+ has the downside of not configuring the default header search paths, so
+ you'll need to specify the full system path configuration on the command
+ line.
+* Use clang as usual, but prefix all arguments to the cc1 process with
+ :option:`-Xclang`.
-For example, to run the print-function-names plugin over a source file
-in clang, first build the plugin, and then call clang with the plugin
-from the source tree:
+For example, to run the ``print-function-names`` plugin over a source file in
+clang, first build the plugin, and then call clang with the plugin from the
+source tree:
-::
+.. code-block:: console
- $ export BD=/path/to/build/directory
- $ (cd $BD && make PrintFunctionNames )
- $ clang++ -D_GNU_SOURCE -D_DEBUG -D__STDC_CONSTANT_MACROS \
+ $ export BD=/path/to/build/directory
+ $ (cd $BD && make PrintFunctionNames )
+ $ clang++ -D_GNU_SOURCE -D_DEBUG -D__STDC_CONSTANT_MACROS \
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -D_GNU_SOURCE \
-I$BD/tools/clang/include -Itools/clang/include -I$BD/include -Iinclude \
tools/clang/tools/clang-check/ClangCheck.cpp -fsyntax-only \
@@ -147,3 +147,4 @@
Also see the print-function-name plugin example's
`README <http://llvm.org/viewvc/llvm-project/cfe/trunk/examples/PrintFunctionNames/README.txt?view=markup>`_
+
