[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-dev] Cleanup of CompilationUnitDeclaration
|
The cleanup is done simply to recover memory - we don't want to hold
onto anything for longer than necessary. If you are hacking the
compiler, I guess you can prevent cleanup to keep the references
around - if that is what you want? References (dependencies) between
types is also recorded as part of the AjState for incremental
compilation.
Andy.
On 25/08/2007, William Huang <breadywhs@xxxxxxxxx> wrote:
>
> Hi, everyone!
>
> I found that the CompilationUnitDeclarations of JDT in the AJDT project,
> will be cleaned up after they are "processed" (including typechecking, flow
> analysis, etc., or the process() method), that is to delete the scope and
> reference info, etc. In the AjPipeliningCompilerAdapter implementation of
> CompilerAdapter, the above info of each CompilationUnitDeclaration can
> hardly exist at the same time. Here comes a question: Is it necessary to
> clear the info of CompilationUnitDeclarations? How can I remain the scope
> the reference info of each CompilationUnitDeclaration for future use?
> ________________________________
> Pinpoint customers who are looking for what you sell.
> _______________________________________________
> aspectj-dev mailing list
> aspectj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>
>
