A test of super constructor calls.

dart/tests/language/src/SuperFirstConstructorTest.dart

Index: dart/tests/language/src/SuperFirstConstructorTest.dart
diff --git a/dart/tests/language/src/SuperFirstConstructorTest.dart b/dart/tests/language/src/SuperFirstConstructorTest.dart
new file mode 100644
index 0000000000000000000000000000000000000000..ffba37d0e86b45de1e9aae9ca5d237984f977ed1
--- /dev/null
+++ b/dart/tests/language/src/SuperFirstConstructorTest.dart
@@ -0,0 +1,28 @@
+// 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.
+
+// Test that the constructor body of a superclass is invoked.
+
+class Super {
+  final argument;

[kasperl, 2012/01/30 06:06:22]

Why is this so complicated with all redirection and the named argument and the
blah and everything? Is it a regression test for a specific issue? Could it be
simplified? If not, maybe adding a comment that explains why it needs to written
this way would be useful.

[ahe, 2012/01/30 07:04:10]

This tests a specific issue in the VM. I have added some comments, and renamed
some variables, but the complexity is the same. I don't know why this bug is
triggered.

+  var fisk;
+
+  Super() : this.named('');
+
+  Super.named(this.argument) {
+    fisk = 'fisk';
+  }
+}
+
+class Sub extends Super {
+  var blah;
+
+  Sub([otherArg = 'otherArg']) : super(), blah = [] {
+    print(otherArg);
+  }
+}
+
+main() {
+  Expect.equals('fisk', new Sub().fisk);
+}