anchor.diff:  
   ==== Setting fields
   
  -Sometimes you need to set a field in a struct sent by reference to a mock function.
  +Sometimes you need to set a field in a struct sent by reference to a mocked function.
   You cannot use the `will_set_contents_of_parameter()` directly since you can't, or even don't want to, know the complete information in the structure.
   But with a little bit of boilerplate in your mock function you can still write to a single field.
   
  
positive.code: So, how do the *Cgreen* stubs work?
  Each `expect()` describes one call to the stub and a call to `will_return()` is included it will aggregate into a list of return values which are used and returned in order as the expected calls arrive.
  
  The `mock()` macro captures the parameter names and the `__func__` property (the name of the stub function).
  *Cgreen* can then use these to look up entries in the return list, and also to generate more helpful messages.
  
  We can now crank out our tests quite quickly...
  
negative.code: 
  This should produce a slightly more user friendly message when things go wrong.
  But, actually, Cgreens default messages are so good that you are encouraged to skip the legacy style and go for the more modern constraints style assertions.
  This is particularly true when you use the BDD style test notation.
  
  IMPORTANT: We strongly recommend the use of BDD Style notation with constraints based assertions.
  
  