Summary: | AST: DCR: BodyDeclaration.getModifiers | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Martin Aeschlimann <martinae> |
Component: | Core | Assignee: | Jim des Rivieres <jeem> |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | fmhwong |
Version: | 2.0 | ||
Target Milestone: | 2.0 M6 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Martin Aeschlimann
2002-04-17 09:29:47 EDT
Each kind of BodyDeclaration has a different set of modifiers that are legal for that type. So even if there was BodyDeclaration.get/setModifiers, we might still want to retain separate spec refinements in each subclass. More fundamentally, it feels like the fact that all BodyDeclarations have modifiers is incidental, rather than something inherent. Would anyone really care if a new kind of BodyDeclaration was added to the language that happens to not have modifiers? I'd bet that anyone going for modifiers also already knows the kind of node they are dealing with. So while it would be possible to make this factoring, I can't see anyone benefitting from this minor change. |