[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [aspectj-users] [newbie] inlining advices, inserting code in each pointcut occurence
- From: Matthew Webster <matthew_webster@xxxxxxxxxx>
- Date: Mon, 31 Jan 2005 14:41:52 +0000
- Delivered-to: firstname.lastname@example.org
- Importance: Normal
This was not a statement about AJDT rather aspects and affected classes
deployed in the field. Requiring every class that has been woven with a
particular aspect to be rewoven when only a small change is made is
unacceptable. This is one reason why (in most cases) advice is not inlined.
Java Technology Centre, MP146
IBM Hursley Park, Winchester, SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
pope <alexandru.popescu@xxxxxxxxx>@eclipse.org on 29/01/2005 04:30:05
Please respond to aspectj-users@xxxxxxxxxxx
Sent by: aspectj-users-admin@xxxxxxxxxxx
Subject: Re: [aspectj-users] [newbie] inlining advices, inserting code
in each pointcut occurence
-----BEGIN PGP SIGNED MESSAGE-----
[quote Matthew Webster::on 1/21/2005 12:44 PM]
| [...] However in general the body of a piece of advice
| is _not_ inlined because this would break modularity i.e. if you changed
| the advice implementation you would have to reweave all your code.
| Matthew Webster
I see the theoritical point here and I agree with it.
But isn't currently this required? (a full rebuild). Maybe just the
incremental mode is taking the
current approach (not quite sure).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
-----END PGP SIGNATURE-----
aspectj-users mailing list