more binary bridging testcode

4 files changed, 11 insertions, 0 deletions

diff --git a/tests/java5/generics/binaryBridging/ThreeA.java b/tests/java5/generics/binaryBridging/ThreeA.java
new file mode 100644
index 000000000..440f748bb
--- /dev/null
+++ b/tests/java5/generics/binaryBridging/ThreeA.java
@@ -0,0 +1,3 @@
+public interface ThreeA {
+  public Number m();
+}
diff --git a/tests/java5/generics/binaryBridging/ThreeB.java b/tests/java5/generics/binaryBridging/ThreeB.java
new file mode 100644
index 000000000..3d89bc61b
--- /dev/null
+++ b/tests/java5/generics/binaryBridging/ThreeB.java
@@ -0,0 +1,3 @@
+public abstract class ThreeB {
+  public abstract Double m();
+}
diff --git a/tests/java5/generics/binaryBridging/ThreeX.java b/tests/java5/generics/binaryBridging/ThreeX.java
new file mode 100644
index 000000000..b402a9f34
--- /dev/null
+++ b/tests/java5/generics/binaryBridging/ThreeX.java
@@ -0,0 +1,3 @@
+public aspect ThreeX {
+  declare parents: ThreeB implements ThreeA;
+}
diff --git a/tests/java5/generics/binaryBridging/readme.txt b/tests/java5/generics/binaryBridging/readme.txt
index b5a28756e..10408c937 100644
--- a/tests/java5/generics/binaryBridging/readme.txt
+++ b/tests/java5/generics/binaryBridging/readme.txt
@@ -3,3 +3,5 @@ Tests that if binary weaving then we create the right bridge methods.
 Test One: Using decp to wire together two types - a generic type that has a bunch of methods that use type variables and a second type that is told to implement a parameterization of the generic type with the decp.
 
 Test Two: Now the horrific method in the supertype is overridden by a combination of covariance and parameterization.
+
+Test Three: inspired by a post to the list.  The abstract method in the subclass should have a bridge method generated alongside it.