Finally I think I understand what AspectJ and HyperJ means. I would like you kindly to improve my reasoning. AspectJ and HyperJ are different ways to modify existent classes. The former deals with in-place-modification and destroys the original class and the latter performs changes in duplicates of the original class but preserves the original class. However all these modifications happens at the level of code implementation (compile time or runtime - I do not know exactly).
Most examples dealing with aspects are based on distribution and persistence and concurrency control and communication systems. So my question is: can we deal with aspects in the same way one deals with separation of concerns? For me separation of concerns is something that starts at the domain level and isomorphically would have a code reasoning structures called aspects or is it HyperJ 's separation of concerns that would be isomorphic? Indeed aspects are concerned with crosscutting concerns. I need help here.
And of course I want to know if Self implements these stuff better or if they are mechanisms that are gracefully dealt with due to delegation's properties. Best wishes Albertina
--------------534322CCCFE8F2C9BECC19B7 Content-Type: text/x-vcard; charset=us-ascii; name="lourenci.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Albertina Lourenci Content-Disposition: attachment; filename="lourenci.vcf"
begin:vcard n:Lourenci;Albertina tel;fax:+55123031 4574 tel;home:+55113818 5362/ 3813-1419 tel;work:Laboratory of Integrated Systems - Polytechnic School USP x-mozilla-html:FALSE url:http://www.lsi.usp.br/~lourenci org:Laboratory of Integrated Systems - Polytechnic School;Department of Electronic Systems Engineering adr:;;Av. Prof. Luciano Gualberto, Trav 3 # 158;São Paulo ;SP;05508-900;Brazil version:2.1 email;internet:firstname.lastname@example.org title:PHD in Architecture and Urbanism note:I am buiilding a prototype-based object oriented knowledge systems to generate sustainable cities fn:Albertina Lourenci end:vcard