Modified unittest to use new argument syntax.

pkg/unittest/mock.dart

 // Copyright (c) 2012, the Dart project authors.  Please see the AUTHORS file
 // for details. All rights reserved. Use of this source code is governed by a
 // BSD-style license that can be found in the LICENSE file.
 
 /**
  * The error formatter for mocking is a bit different from the default one
  * for unit testing; instead of the third argument being a 'reason'
  * it is instead a [signature] describing the method signature filter
  * that was used to select the logs that were verified.
  */
@@ skipping 414 matching lines @@
     }
     return rtn;
   }
 
   /** Apply a unit test [Matcher] to the [LogEntryList]. */
   LogEntryList verify(Matcher matcher) {
     if (_mockFailureHandler == null) {
       _mockFailureHandler =
           new _MockFailureHandler(getOrCreateExpectFailureHandler());
     }
-    expect(logs, matcher, filter, _mockFailureHandler);
+    expect(logs, matcher, reason:filter, failureHandler: _mockFailureHandler);

[Jennifer Messerly, 2012/10/26 02:57:05]

I think this would read better if it was called "failure" or "onFailure"

[gram, 2012/10/26 22:26:27]

It's a class, not a method, so it should be a noun, not a verb.

[Jennifer Messerly, 2012/10/26 22:50:16]

Makes sense. I was assuming it was a callback :)

btw, small nit, +1 space after colon: "reason: filter"

     return this;
   }
 
   /**
    * Iterate through the list and call the [validator] function with the
    * log [List] and position. The [validator] should return the number of
    * positions to advance upon success, or zero upon failure. When zero is
    * returned an error is reported. [reason] can be used to provide a
    * more descriptive failure message. If a failure occurred false will be
    * returned (unless the failure handler itself threw an exception);
@@ skipping 1004 matching lines @@
       }
     }
   }
 
   /** Clear both logs and behavior. */
   void reset() {
     resetBehavior();
     clearLogs();
   }
 }