anchor.diff:  }
   -----------------------
   
  -I've been a bit naughty.  As each test runs in it's own process, I
  +I've been a bit naughty.  As each test runs in its own process, I
   haven't bothered to free the pointers to the paragraphs.  I've just
   let the operating system do it.  Purists may want to add the extra
   clean up code.
  
positive.code: 
  Where are the assertions?
  
  Unlike our earlier stub, 'reader()' can now check it's parameters.  In
  object oriented circles, an object that checks it's parameters as well
  as simulating behaviour is called a mock object.  By analogy
  'reader()' is a mock function, or mock callback.
  
  
negative.code: you need to tackle the problem.
  
  To prevent segmentation faults and other problems bringing down the
  test suites, *Cgreen* runs every test in its own process.
  
  Just before calling the 'setup' function, *Cgreen* 'fork()''s. The main
  process waits for the test to complete normally or die. This includes
  the calling the 'teardown' function, if any. If the test process dies,
  an exception is reported and the main test process carries on.
  
  