paulberry@google.com
238ea2c84e
Two issues: 1. Some exceptions don't derive from Exception (for example NoSuchMethodError). So to avoid problems in checked builds, CaughtException.exception needs to have type Object. 2. When an exception is caught by the unittest framework, it prints it using its toString() method. So in order to see the stack trace of the CaughtException nested in an AnalysisException, we need AnalysisException's toString() to print both the exception and its cause (if any). R=brianwilkerson@google.com, jwren@google.com, scheglov@google.com Review URL: https://codereview.chromium.org//304293010 git-svn-id: https://dart.googlecode.com/svn/branches/bleeding_edge/dart@37186 260f80e4-7a28-3924-810f-c04153c831b5
This code is part of an experimental port of the Editor's analysis engine from Java to Dart. While we will continue to support the Java version of the analysis engine and the services built on it, we also intend to provide the same services to Dart-based applications. This is very early code and we expect it to change, possibly in significant ways. While we are eager to see other people make use of the analysis engine, we also want to be clear, in case you are interested in doing so, that the current API's should in no way be considered to be stable.
In particular, this code was automatically translated from the Java implementation. The Java implementation that was translated is still under development and will continue to change over time. The translator that was used is still under development and the output produced by the translator will change over time. Therefore, the API presented by this code will change. In addition, any edits made to this code will be overwritten the next time we re-generate this code.
If you are interested in using this code, despite the disclaimer above, fantastic! Please let the editor team know so that we can get a sense of the interest in it. Also, feel free to ask questions and make requests for additional functionality.