anchor.diff:  int split_words(char *sentence);
   -------------------------------
   
  -...and to get the code to link we need a stub function in 'words.c'...
  +...and to get the code to link we need a stub function in +words.c+...
   
   [source,c]
   -------------------------------
  
positive.code: 
  Job done.
                           
  Possible other extensions include reporters that write to <emphasis>syslog,
  talk to IDE plug-ins, paint pretty printed documents or just return a boolean
  for monitoring purposes.
               
  Automaticaly tests collector	
  ----------------------------
  
  The collector tool
  ~~~~~~~~~~~~~~~~~~
              
  When we want to add a new test, we open the test script and create a new
  void function. So we add the name of the function inside of TestSuite.
  				
  In summary each new test added we should added inside of TestSuite too.                
  
  
  The collector tool change this
  boring behaviour. The idea is to save work of add every tests written inside
  of 'TestSuite'. Basically each test is to be declared with the macro
  Ensure in which is automatically inserted
  inside of 'TestSuite'.
                                                            
  Example
  ~~~~~~~
              
  To use the collector tool we need to modify the definition of each functions.
  Before we used:
  
  [source,c]
  -----------------------
  void one_should_assert_char_equal_to_one() {
  	char x = 1;
  	char y = 1;
      assert_equal(x, y);
  }
  -----------------------
  
  Now we need to rewrite to:
  
  [source,c]				
  -----------------------
  Ensure one_should_assert_char_equal_to_one() {
  	char x = 1;
  	char y = 1;
      assert_equal(x, y);
  }
  -----------------------
                  
  For each writen test, we must declared like Ensure type. 
  It is a C macro and tell to collector that this test should be put inside the TestSuite.                
   
  
  In the TestSuite we don't more need to write the testes with compound the TestSuite. Just let
  like:
  
  [source,c]
  -----------------------                
  TestSuite *assertion_tests() {
      TestSuite *suite = create_test_suite();
      add_tests();
      return suite;
  }                
  -----------------------     
                             
  Assuming that our test script is the file +assertion_tests.c+, 
  running the 'collector' we have:
  				
  -----------------------                
  ./collector assertion_tests.c
  -----------------------
  
  The finally result in test script is:
  
  [source,c]
  -----------------------
  Ensure one_should_assert_char_equal_to_one() {
  	char x = 1;
  	char y = 1;
      assert_equal(x, y);
  }
  
  TestSuite *assertion_tests() {
      TestSuite *suite = create_test_suite(&one_should_assert_char_equal_to_one);
      add_tests();
      return suite;
  }
  -----------------------
             
            
  The tool read all script, do the necessary substituitions and write to the
  original file.
  So just add a new test and run the collector tool to adjust automatically the
  TestSuite.
             
  
  [appendix]
  Revision History
  
negative.code: about the methods in the 'TestReporter' structure.
               
  The TestReporter structure
  ~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  The *Cgreen* 'TestReporter' is a pseudo class that looks
  something like...
  