RE: [Mockobjects-java-dev] AOP : Aspect Oriented Programming

[Tim M. <tim...@po...>]

The kicker has always been getting good IDE support to work out what got
woven in - not sure if they have made any progress on this? There are some
good examples of weaving in patterns like observer etc. which I thought were
good at the time I looked at it - and it did fire my brain a year back when
working on the original mock stuff but I never found a good moment to use
it.

There were also some issues with co-variance and contravariance at the time
I looked at it - they had arbitrarily chosen the wrong way and broke the
rules, but I remember Gregor saying they would consider changing it.

Tim

> -----Original Message-----
> From: moc...@li...
> [mailto:moc...@li...]On Behalf Of
> Steve Freeman
> Sent: 22 August 2001 12:54 am
> To: moc...@li...
> Subject: Re: [Mockobjects-java-dev] AOP : Aspect Oriented Programming
>
>
> I've known about this stuff for a while but have quite never
> found the time to do anything with it.
>
> Time to give it a try?
>
> Steve
>
>
> ----- Original Message -----
> From: "Vincent Massol" <vm...@oc...>
> To: <moc...@li...>
> Sent: Monday, August 20, 2001 2:10 PM
> Subject: [Mockobjects-java-dev] AOP : Aspect Oriented Programming
>
>
> > I have discovered AOP this week end (AspectJ) and found it very very
> > interesting, especially for unit testing purposes. I highly
> suggest that you
> > take 30 minutes to an hour to read the "getting started" paper
> > (http://aspectj.org/doc/gettingStarted/index.html).
> >
> > I find the idea great. In a few words, the idea is that there exist some
> > crosscutting aspects (hence the name: AspectJ) that encompasses several
> > methods. For example, let's say you want to log the entry and exits of
> > methods. This is a general pattern. In java, it would be very
> difficult to
> > materialize this aspect. You would have to add log statements at the
> > beginning and end of each method, but still you would not have
> captured the
> > pattern. Also, if you add a new method, you have to remember to add log
> > statements.
> >
> > AspectJ let you describe aspects in its own semantic (near
> java). Then, you
> > apply the aspect compiler which will transform the code in java
> and invoke
> > the javac compiler to compile it.
> >
> > It is very very powerful. You can say things like verify that
> such method is
> > only called by such other method when it is in such context. There are
> > better examples (with code) given in the paper highlighted above.
> >
> > Just wanted to let you know
> > -Vincent
> >
> >
> > _______________________________________________
> > Mockobjects-java-dev mailing list
> > Moc...@li...
> > http://lists.sourceforge.net/lists/listinfo/mockobjects-java-dev
> >
> 2‡$¡¸ÞrÛ#jözùšŠX§‚X¬´Ê’†ãyËl«ÚuëåŠËl²‹«qç讧zØm¶Ÿÿ–+-²Ê.­ÇŸ¢¸
> ë–+-³ùb²Ø§~æ¡É(n7œ¶ÈÚ½§^