Le 18 août 2009 à 13:19, Rickard Öberg a écrit :
Hey,
If a mixin implements an interface, but is marked as abstract, it
has until now been required that it uses @This injections in order
to call the rest of the methods. Also, if a mixin calls another
public method which is a part of the composite interface, then one
would have to use a @This injection to make sure that the call went
through the proxy (and concerns/sideeffects).
Today I have been experimenting with allowing mixins to call methods
that are not implemented in abstract mixins, and have them be
automatically routed to the composite. Similarly, if a mixin calls
another method it is automatically routed through the proxy without
the mixin having to do anything.
Sounds perfect for me, I sometimes forgot to call @This, now I am used
to, but if I could get rid of it =-> +1
I think that it will also help findbugs, metrics and refactoring tools
understand more what's really happening behind the wheel.
my 2 cents,
Philippe
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
