I am interested in aspects as for crosscutting concerns they are useful. I am now using Traits in my code and it works well indeed. The problem with them is that I have to pepper them around in classes where with aspects, I could define pointcuts in a single place with definitions (I used that in Java with Spring for example).
I am not interested in performance, this is mostly for development activities and the final code may well use Traits that I could put in the classes with some source code generation and recompiles. One key aspect would be to do accounting of the system usage in order to bill the users according to their usage of the features. Something like AspectS looked quite integrated language wise. Some reference work I use conceptually speaking: http://www.amazon.com/Aspect-Oriented-Software-Development-Use-Cases/dp/0321268881 http://aosd.net/archive/2003/*jacobson*-aosd-2003.ppt Regards, Phil
