Summary: | problem with new/FieldInitializerJoinPoints.java | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Ganesh Sittampalam <ganesh> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | NEW --- | QA Contact: | |
Severity: | minor | ||
Priority: | P3 | CC: | eh-ajdev |
Version: | DEVELOPMENT | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Ganesh Sittampalam
2004-08-20 05:39:23 EDT
(Some more comments about the general specification of this issue; I think they belong best with this bug) Is it specified somewhere that the initializer for a static final field with a constant value should be omitted from the bytecode, but that it shouldn't be for instance fields? I know that the ConstantValue attribute only applies to static fields and must be supported by a JVM (JVMS 4.7.3), but I can't find anything that actually insists that it be used for them or that the putstatic be omitted. Making the semantics of the language dependent on a particular compiler implementation decision, even one that is widely used, seems a bit dangerous. |