[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] [newbie] inlining advices, inserting code in each pointcut occurence



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.

Matthew Webster
AOSD Project
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
http://w3.hursley.ibm.com/~websterm/

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


To:    aspectj-users@xxxxxxxxxxx
cc:
Subject:    Re: [aspectj-users] [newbie] inlining advices, inserting code
       in each pointcut occurence


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[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

[/quote]

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).

- --
:pope
[the_mindstorm]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFB+xFNTTDTje0R2dgRAk6tAJ9pggBHHsJOXSd7L675y2Fg+8YsIQCePHYq
DAdklpVmBBdfKsu78c/OmrI=
=dttd
-----END PGP SIGNATURE-----
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/aspectj-users