Community
Participate
Working Groups
When the display fails to resolve an expression, the client prints "<inspection target>: " as usual, but it does not print a result to the display. Suggest printing "(failed to resolve)" the way "(no explicit return value)" is printed for declarations. 1. In the debugger display window, enter "int i=0;", highlight, and display. Client prints "(no explicit return value)" 2. Type a nonexistant variable name, highlight, and display. Client currently prints nothing. NOTES: DW (6/13/01 11:36:46 AM) Defer.
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.