Summary: | Feature: Resolution failure notification (1GF9OG5) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jared Burns <jared_burns> |
Component: | Debug | Assignee: | Jared Burns <jared_burns> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Jared Burns
2001-10-10 22:16:52 EDT
In the current code base, entering a non-resolvable name, results in an error dialog with "X cannot be resolved". Fixed. Please verify. Verified that the dialog pops up. We should still print out "(failed to evaluate)" in the display view. Not doing so breaks the formatting. For instance: Enter three queries on the string grah (grah.toString, grah.asdf, grah.toString) yields: grah.toString() (java.lang.String) "grah" grah.asdf grah.toString() (java.lang.String) "grah" grah.foo() (no explicit return value) If we print an error message, it would (should) look like: grah.toString() (java.lang.String) "grah" grah.asdf (evaluation failed) grah.toString() (java.lang.String) "grah" foo() (no explicit return value) Feature Request VERSION: 122++ Added "(evaluation failed)" on failure. Please verify. Verified. This is a test of Bugzilla/Opera. This is a test of Bugzilla/Opera. This is a test of Bugzilla/Opera. This is a test of Bugzilla/Opera. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. This is a test. |