Re: [abc] Jastadd compile bugs

From: Pavel Avgustinov <pavel.avgustinov@magdalen.oxford.ac.uk>
Date: Mon Jan 16 2006 - 17:21:11 GMT

Another two interesting problems:

---
interface I { }
public class NullError { }
---
This causes jastadd to fail with an error message of 'null'.
---
public class Test {
    public polyglot.types.ClassType foo;
    public void bar() {
        foo.toString();
    }
}
---
(This bug prevents jastadd from compiling abc, among others.) Jastadd
claims there are two 'most specific methods' for the toString call --
polyglot.types.Type.toString() and java.lang.Object.toString().
polyglot.types.Type is a superinterface of ClassType, and defines a
method toString() (for the sake of attaching javadoc to it). It seems
like jastadd doesn't consider Object to be a supertype of the Type
interface when determining the most specific method the call could refer
to. I had no luck reducing the test case to something that didn't
involve the polyglot class hierarchy, strangely.
- P
Received on Mon Jan 16 17:21:35 2006

This archive was generated by hypermail 2.1.8 : Tue Jan 17 2006 - 10:30:09 GMT