From: Mikio T. <mik...@gm...> - 2012-07-18 10:30:13
|
I have some questions and comments. 2012/7/18 David Cunningham <dc...@us...>: > Maybe get rid of x.l.Exception? What is this? > Definitely get rid of x.l.RuntimeException Done. > Disable exception wrapping in managed backend. > NativeRep exceptions to java equivalents. > x.l.Throwable, NPE, ClassCast, ArrayBounds, StringBounds, To use NativeRep to java equivalents, we basically not able to change the type hierarchy. For example, the super type of x10.lang.NullPointerException, which is java.lang.NullPointerException in generated Java code, will be java.lang.RuntimeException. We may be able to skip j.l.RuntimeException and treat it as a single leaf child of x10.lang.Exception by modifying RuntimeType and the families, but it requires manual modification and drastic change of the exception hierarchy from Java is not realistic. > Change assert codegen to throw x10.lang.AssertionError instead of > java.lang.AssertionError This is also done. -- Mikio |