anchor.diff:  paragraphs than it has to write the code.
   
   
  -Using Cgreen with C++
  -^^^^^^^^^^^^^^^^^^^^^
  -
  -This is actually quite simple. If you have installed the Cgreen
  -library for C++ all you have to do is
  +Using Cgreen with C{pp}
  +~~~~~~~~~~~~~~~~~~~~~~~
  +
  +The above example, as well as most of this guide, shows how to uses
  +*CGreen* with C. You can also use *CGreen* with C++. This is actually
  +quite simple. If you have installed the *Cgreen* library for C{pp} all you
  +have to do is
   
     * Place your tests in the `cgreen` name space by surrounding them
       with `namespace cgreen {}`
   
  -  * Use the C++ version of the library when linking (`-lcgreen++` or
  +  * Use the C{pp} version of the library when linking (`-lcgreen{pp}` or
       something similar)
   
  +There is one extra feature when you use C++, the `assert_throws` function.
   
   Building Cgreen test suites
   ---------------------------
  
positive.code: constraint macros. This is caused by the macros using argument strings
  to produce nice failure messages.
  
  BDD Style vs. TDD Style
  ~~~~~~~~~~~~~~~~~~~~~~~
  
  
negative.code: documentation you'll need.
  
  The `assert_that()` call is the primary part of an assertion, which is
  complemented with a constraint, in this case `is_equal_to()`, as a
  parameter. This makes a very fluent interface to the asserts, that
  actually reads like English.
  
  NOTE: Sometimes you just want to fail the test explicitly, and there
  is a function for that too, `fail_test(const char *message)`. And
  there is a function to explicitly pass, `pass_test(void)`.
  
  Assertions send messages to *Cgreen*, which in turn outputs the
  results.
  
  
  The Standard Constraints
  ~~~~~~~~~~~~~~~~~~~~~~~~
  
  Here are the standard constraints...
  
  