Fix issue with optional named parameters.

Fix issue with optional named parameters.
Update tests.
Committed: https://code.google.com/p/dart/source/detail?r=12214

[hausner, 2012-09-11 17:37:53]

lgtm

https://chromiumcodereview.appspot.com/10911217/diff/1/tests/language/optiona...
File tests/language/optional_named_parameters_test.dart (right):

https://chromiumcodereview.appspot.com/10911217/diff/1/tests/language/optiona...
tests/language/optional_named_parameters_test.dart:65: Expect.equals(20,
F10(20));  /// 01: runtime error
The test has to run with --reject_named_argument_as_positional to trigger these
runtime errors, right? Don't you have to include
VMOptions=--reject_named_argument_as_positional at the top of this file?

[regis, 2012-09-11 18:02:35]

Thansk!

https://chromiumcodereview.appspot.com/10911217/diff/1/tests/language/optiona...
File tests/language/optional_named_parameters_test.dart (right):

https://chromiumcodereview.appspot.com/10911217/diff/1/tests/language/optiona...
tests/language/optional_named_parameters_test.dart:65: Expect.equals(20,
F10(20));  /// 01: runtime error
On 2012/09/11 17:37:53, hausner wrote:
> The test has to run with --reject_named_argument_as_positional to trigger
these
> runtime errors, right? Don't you have to include
> VMOptions=--reject_named_argument_as_positional at the top of this file?

No, we always want to detect this error. The flag only relaxes the rules when
passing named arguments to positional parameters in [], but not when passing
positional arguments to named parameters in {}. This is actually what this cl
fixes.