anchor.diff:                 end, AppList)];
   format_exception(?SIN_EXEP_UNPARSE(_,
                                      {warnings, Warnings, _AppList})) ->
  -    lists:map(fun(Warning) ->
  +    [lists:map(fun(Warning) ->
                         dialyzer:format_warning(Warning)
  -              end, Warnings);
  +              end, Warnings), "~n"];
   format_exception(Exception) ->
       sin_exceptions:format_exception(Exception).
   
  
positive.code:             useful information. You can get around this by asking the
              dialyzer task to ignore certain applications. Do this in
              your build config with the following entry.  <break>  <break>
              {plt_ignore, [some_app1, some_app2]}.  <break>  <break>
              The downside, of course, is figuring out which apps actually
              have the problem. This task tries to help by printing out a
              list of applications that where under analysis when the blowup
  
negative.code:      race_conditions,
       behaviours,
       unmatched_returns,
       underspecs].
  