Hi James,
I think it still has a problem when multiple this constructors are
involved. In that case, the advice code would be executed twice (or more
times) depending on how many this() calls there are between constructor.
In this case the initialization pointcut comes in handy, cause it
matches t
very nice ;)
Andy.
2008/9/9 Simone Gianni <[EMAIL PROTECTED]>
> What about this :
>
> public aspect CheckingWithSimplestAspectJEver {
>
>pointcut constructor(A inst) : execution(A+.new(..)) && this(inst);
>
>after(A inst) : constructor(inst) {
>if (inst.getClass().equals(
>
Simone,
You are brilliant.
This also works with construction via reflection, even within a
delegate, and is orders of magnitude faster than your first solution.
Thanks so much. =)
___
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.ecl
"Andrew" == Andrew Eisenberg <[EMAIL PROTECTED]> writes:
Andrew> I don't know why you are receiving so many digests [...]
Mailman will send a digest when the size (KB) of the to-be-sent mail reaches a
(configurable) threshold. Rampant overquoting means that the threshhold is
reached quic
In the future please send administrative requests like this to
[EMAIL PROTECTED]
I don't know why you are receiving so many digests and I am not the
list administrator so I can't help you directly, but instead of daily
digests, you can choose to subscribe to the rss feed or choose to not
receive a
Dear fellow subscribers to aspectj-users,
My account is set to digest mode. If I'm not mistaken, the "digest" below is the
sixth I received today.
I'm the only one thinking that "digest" should really mean "daily digest"?
mpm
Em Ter, Setembro 9, 2008 5:01 pm, [EMAIL PROTECTED] escreveu:
> Send
2008/9/9 Dean Wampler <[EMAIL PROTECTED]>:
> Symmetric AOP is the idea that aspects are used as commonly as classes in an
> app and that aspects have the same "first-class" nature.
I would even go so far to say that in truly symmetric AOP there is no
notion of a class any more. Everything is an as
What about this :
public aspect CheckingWithSimplestAspectJEver {
pointcut constructor(A inst) : execution(A+.new(..)) && this(inst);
after(A inst) : constructor(inst) {
if (inst.getClass().equals(
thisJoinPointStaticPart.getSourceLocation().getWithinType()))
S
Symmetric AOP is the idea that aspects are used as commonly as classes
in an app and that aspects have the same "first-class" nature. In
contrast, in Asymmetric AOP, the aspects are used more as "adjuncts"
to classes, which are used to modularize most of the code in the app.
So, AspectJ is
What about this :
public aspect CheckingWithSimplestAspectJEver {
pointcut constructor(A inst) : execution(A+.new(..)) && this(inst);
after(A inst) : constructor(inst) {
if
(inst.getClass().equals(thisJoinPointStaticPart.getSourceLocation().getWithinType()))
System
A slight clarification. Aspects are still "first-class" in AspectJ...
On Sep 9, 2008, at 7:56 AM, Dean Wampler wrote:
Symmetric AOP is the idea that aspects are used as commonly as
classes in an app and that aspects have the same "first-class"
nature. In contrast, in Asymmetric AOP, the aspe
Hi all,
sorry for this question that is not tied to AspectJ, but yesterday I heard for
the first time the term "symmetric aop", but I dind't get the meaning. Anyove
can give me info or pointers about?
Thanks,
Luca
___
aspectj-users mailing list
aspectj
12 matches
Mail list logo
