| Summary: | Unqualified variable names could be resolved | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Stefan Henss <stefan.henss> |
| Component: | Recommenders | Assignee: | Marcel Bruch <marcel.bruch> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Stefan Henss
Is IntelligentCompletionContext.findMatchingLocalVariable(String) what you want? We could make this public if this meets your requirements. Yes, indeed, using this method I could handle the problem. (In reply to comment #2) > Yes, indeed, using this method I could handle the problem. Here you go: public Variable findMatchingVariable(final String variableName) It's not tested. Feel free to change it if you experience any exceptions. Only take care that as little as possible jdt.compiler AST nodes are propagated to outside world. Please note, it searches the locals and fields declared in the current compilation unit but ignores inherited fields.Enabling this requires reworking the context and binding it to WALA or JDT. Since WALA integration is not perfectly stable yet I would postpone this for a while. Closing this issue. Please give latest dev build (v0.5) a try: http://download.eclipse.org/recommenders/updates/dev/e37/ http://download.eclipse.org/recommenders/updates/dev/e42/ Closing this issue. Please give latest dev build (v0.5) a try: http://download.eclipse.org/recommenders/updates/dev/e37/ http://download.eclipse.org/recommenders/updates/dev/e42/ |