Summary: | Modify BcelObjectType for easier subclassing | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Andrew Clement <aclement> |
Component: | Compiler | Assignee: | Andrew Clement <aclement> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | lzhou |
Version: | DEVELOPMENT | ||
Target Milestone: | 1.5.1 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Andrew Clement
2005-01-07 05:30:30 EST
Hi larry, you should get copied on this update to the enhancement request I created. I have one more question for you, when you say 'In our situation, we know when a particular BcelObjectType is not needed anymore.' - can you possibly describe how you know? Are you doing LTW and once loaded you want to throw them away? thanks, Andy. AspectJ1.5.1 included tidyup logic for the Bcel delegates meaning they can be 'hollowed out' when weaving is completed. It may have to be activated in non-LTW environments with the option -Xset:runMinimalMemory=true - for LTW it is the default. |