Using 'interface' and 'abstract' for methods should produce error

compiler/javatests/com/google/dart/compiler/parser/ClassesInterfaces.dart

Index: compiler/javatests/com/google/dart/compiler/parser/ClassesInterfaces.dart
diff --git a/compiler/javatests/com/google/dart/compiler/parser/ClassesInterfaces.dart b/compiler/javatests/com/google/dart/compiler/parser/ClassesInterfaces.dart
index 8001649941c3f64f71be015722ec78f8dc623e86..72bc4c62d71e5b4572ac67e6b59d2b091ff89221 100644
--- a/compiler/javatests/com/google/dart/compiler/parser/ClassesInterfaces.dart
+++ b/compiler/javatests/com/google/dart/compiler/parser/ClassesInterfaces.dart
@@ -111,16 +111,16 @@ class Baz extends Kuk implements A, B, C {
   Baz(x, y, z) : super(x, y, z) {}
 }
 
-interface Foo extends D, E {
-  bar();
-}
-
+//interface Foo extends D, E {

[Brian Wilkerson, 2012/10/27 15:13:25]

It looks like this could all be converted to use classes by replacing 'extends'
with 'implements'. I'm not sure whether it would be a valuable test or not
though.

[Brian Wilkerson, 2012/10/27 15:13:25]

ditto

[scheglov, 2012/10/27 18:08:47]

Done.

+//  bar();
+//}
+//
 // Test bounds on type parameters
-interface Bar<K extends Foo, V> extends Foo {
-}
-
-interface Bar<K extends Foo, V extends Foo> extends Foo {
-}
-
-interface Bar<K, V extends Foo> extends Foo {
-}
+//interface Bar<K extends Foo, V> extends Foo {
+//}
+//
+//interface Bar<K extends Foo, V extends Foo> extends Foo {
+//}
+//
+//interface Bar<K, V extends Foo> extends Foo {
+//}