anchor.diff:  %% @todo Explain in documentation why we use a process to handle test input.
   %% @doc etap is a TAP testing module for Erlang components and applications.
   %% This module allows developers to test their software using the TAP method.
  -%% 
  +%%
   %% <blockquote cite="http://en.wikipedia.org/wiki/Test_Anything_Protocol"><p>
   %% TAP, the Test Anything Protocol, is a simple text-based interface between
   %% testing modules in a test harness. TAP started life as part of the test
   %% harness for Perl but now has implementations in C/C++, Python, PHP, Perl
   %% and probably others by the time you read this.
   %% </p></blockquote>
  -%% 
  +%%
   %% The testing process begins by defining a plan using etap:plan/1, running
   %% a number of etap tests and then calling eta:end_tests/0. Please refer to
   %% the Erlang modules in the t directory of this project for example tests.
  
positive.code: %% copies of the Software, and to permit persons to whom the
  %% Software is furnished to do so, subject to the following
  %% conditions:
  %% 
  %% The above copyright notice and this permission notice shall be
  %% included in all copies or substantial portions of the Software.
  %% 
  %% THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
  %% EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
  %% OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
  
negative.code:     case [IsSkip, Result] of
          [_, true] ->
              etap_server ! {self(), pass, Desc},
              true;
          [1, _] ->
              etap_server ! {self(), pass, Desc},
              true;
          _ ->
              etap_server ! {self(), fail, Desc},
              false
      end.
  