[
https://issues.jboss.org/browse/ROASTER-76?page=com.atlassian.jira.plugin...
]
Shoji Kuzukami edited comment on ROASTER-76 at 7/10/15 3:20 AM:
----------------------------------------------------------------
Really? It is too heavy to support fully the specification.
But I yet want to know which design guideline is preferable, 'A local class must be
contained in the #getNestedClasses() of the directly enclosing method' or
'contained in the one of indirectly enclosing "Type"'?
Is it preferable that "directly enclosing method" design?
It's happy for me that a local class is removed from #getNestedClasses() of
'indirectly enclosing "Type"' because I can avoid the bug of "The
getQualifiedName() for local class" in my application.
was (Author: kuzukami):
Really? It is too heavy to support fully the specification.
But I yet want to know which design guideline is preferable, 'A local class must be
contained in the #getNestedClasses() of the directly enclosing method' or
'contained in the one of indirectly enclosing "Type"'?
Is it preferable that "directly enclosing method" design?
That's happy for me that a local class is removed from #getNestedClasses() of
'indirectly enclosing "Type"' because I can avoid the bug of "The
getQualifiedName() for local class" in my application.
Which one encloses a local class.
---------------------------------
Key: ROASTER-76
URL:
https://issues.jboss.org/browse/ROASTER-76
Project: Roaster
Issue Type: Quality Risk
Components: API, JDT
Affects Versions: 2.14.0.Final
Reporter: Shoji Kuzukami
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)