Ryan Heise wrote:
> The idea of aspects cutting across classes is interesting but the
> current design of AspectJ seems to be limited in what places you can cut
> through a class. Here are the defined entry points:
>
> before
> after
> catch
> finally
No, it seems to can do more according to the aj primer. E.g. "automatic
composition".(I had no time to read+understand the full primer, I'm
going to dig through this this weekend)
> <brain.dump>
> hmm.. I wonder whether the idea of aspects can be generalised even
> further than the basic object + aspects idea. Maybe a class can be
> defined in terms of a number of intersecting aspects...
> </brain.dump>
The most important thing is to keep a certain grade of encapsulation,
IMHO AspectJ has to manage this... Could be done by Interfaces (? define
an interface for every object?). Sounds possible, but is AOP
(standalone) as powerful as OOP+AOP?
> It would not be too difficult to implement one since its main task is
> copying lines of code from the Aspect into intersected classes.
It's one thing to compete with an existing product and another to
compete with Xerox PARC in developing a new programming paradigm. If at
all, IMHO we should concentrate in pushing the development of aj and or
in general the application of aop to java, so when the question of a
reimplementation comes we'd have a good product to reimplement.
regards.mark.a.m
_______________________________________________
General maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/general
