anchor.diff:  
   If you require another custom reporter you need to resort to the
   standard, programatic, way of invoking your tests. For now...
  +
  +
  +Ignoring Tests
  +~~~~~~~~~~~~~~
  +
  +Sometimes you find that you need to temporarily remove a test, perhaps
  +to do a refactoring with a failing test. Ignoring it will allow you to do the
  +refactoring while still in the green.
  +
  +An old practice is then to comment it out. That is a slightly cumbersome
  +and hazardous habit as there is no indication of a missing test if you
  +forget to uncomment it when you are done.
  +
  +*Cgreen* offers a much better solution. You can just add an 'x' infront
  +of the `Ensure` for the test.
  +
  +[source, C]
  +----------------------------
  +...
  +xEnsure(Reader, ...) {
  +  ...
  +}
  +...
  +----------------------------
  +
  +With this method, it is a one character change to temporarily ignore,
  +and un-ignore, a test. It is also easily found using text searches through
  +a complete source tree. And in a near future *Cgreen* will also tally the
  +ignored tests, so it is visible when you run your tests.
   
   
   Mocking functions with Cgreen
  
positive.code: --------------------------
  
  The `-fPIC` means to generate 'position independent code' which is
  required if you want to load the library dynamically.
  
  How to build a dynamically loadable shared library might vary a lot
  depending on your platform. Can't really help you there, sorry!
  
negative.code: 
  All done.
  
  === Mocks Are... ===
  
  Using mocks is a very handy way to isolate a unit and catch and
  control calls to external units. Depending on your style of coding two
  