[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [aspectj-dev] Change in the interface tools should use to invoke the compiler
|
One benefit of this change is a reduction in the overhead involved
when invoking the compiler. This becomes significant when the actual
compile time is small, such as for small projects or (more usefully)
incremental builds. I measured a 15% improvement when performing an
incremental build of 5 AspectJ projects in AJDT:
http://www.eclipse.org/ajdt/newfeatures/#compiler20070116
--Matt
On 16/01/07, Helen Hawkins <HAWKINSH@xxxxxxxxxx> wrote:
Work has been going on as part of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=148190 to revisit the
interface tools use to invoke the compiler ( the need of which has grown
out of an acknowledgment of the differing requirements between various
tools that use Ajde). This has now been checked in to the AspectJ codebase
and will be available in the next development build. The corresponding
updates have also been checked in to AJDT (HEAD and branch 1.4) and again
will be available in the next development builds for these two streams.
As part of these changes a new aspectj project ajde.core has been created,
along with the corresponding bundle projects org.aspectj.ajde.core and
org.aspectj.ajde.core.tests. The idea being that ajde.core contains what is
required to drive the compiler and receive feedback about it for tools that
wish to handle the views/ui representation of the model themselves (for
example AJDT), and ajde contains all the information that tools who do not
want to handle their own views use (for example ajbrowser).
The bug contains more details, in particular comment #38
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=148190#c38) describes how
tools should use the new interface and points at examples of the different
usage.
If you have any problems/questions please let me know,
Thanks, Helen
