| Summary: | Would like to inspect from the context of an inspect result (1GDKNZ7) | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | John Wiegand <John_Wiegand> |
| Component: | Debug | Assignee: | Darin Wright <darin.eclipse> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | pesenson_leonid |
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Windows NT | ||
| Whiteboard: | |||
| Bug Depends on: | 1546, 10318 | ||
| Bug Blocks: | |||
|
Description
John Wiegand
PRODUCT VERSION: 105 *** Bug 6975 has been marked as a duplicate of this bug. *** This is now implemented, but could use some refinement. The "context" in which an expression is compiled is that of the selected variable/value in the variable/expression view. You can now type expressions in the "detail/toString" area a la VAJ. The "compilation context" may be confusing to the user. This also exposes our expression eval limitations related to class file deployment - i.e. no expression evaluations when there is no source, and when in a system package (java.lang). Should now be able to fix code assist to reflect selected variable type using new code assist API. (AST Expression eval still needed to fix eval problems). Implemented. Please verify (darin W). Verified code assist works properly. Now we await AST evals to make this function more usefult. |