Summary: | Respect final classes | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Wes Isberg <wes> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | REOPENED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | ||
Version: | 1.2 | ||
Target Milestone: | 1.5.0 M4 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Wes Isberg
2003-12-02 15:31:17 EST
The discussions around this issue continue to circulate periodically. It would be nice to give AspectJ programmers who want some level of assurance/control a way to get it. Perhaps a -XrespectFinal[Types?] flag in AJ5 M4 that does not allow modifications to final types? (Caution - the issue is quite tricky, we have to separate out what the 'user' considers a modification - such as an ITD, or maybe execution advice, from modifications that arise out of current implementation strategies (e.g. a perthis() aspect where 'this' has a final type). It feels like the latter should be allowed even though it touches the bytes of the final class. Otherwise we end up with semantics that are based on a current implementation. Let's look at it as part of the M4 milestone. We're not going to get to this in AJ 1.5.0. Marking as "LATER" for consideration in 1.5.1 and future release planning. LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated. |