| Summary: | [templates] variable 'iterable' should also include member scope fields | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | thomas menzel <tmenzel> |
| Component: | Text | Assignee: | JDT-Text-Inbox <jdt-text-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P5 | CC: | arrg.ch, daniel_megert, manuel.bork |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
thomas menzel
NOTE: You could implement your own variable resolver and use that one in the template. The doc states that ${iterable} "Evaluates to a proposal for an iterable or array visible in the current scope.".
Here: http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.jdt.doc.user%2Fconcepts%2Fconcept-template-variables.htm
So either the code or the doc needs fixing.
It seems that most 'simple' variables (iterable, array, collection, etc.) behave this way (suggest only locals).
The 'complex' variable ${id:var(type)} works on all scopes.
*** This bug has been marked as a duplicate of bug 117215 *** |