[PRL] legacy code and AOP

[Therapon Skotiniotis]

I know that AspectC was in the works 

  http://www.cs.ubc.ca/labs/spl/projects/aspectc.html

The main theme there was (I have not followed up on their recent results) 
an AOP language to provide better modularity in OS kernel code


There is also TinyC(^2)
  http://citeseer.ist.psu.edu/zhang03tinycsuptowards.html
(however citeseer seems to be down) 

A more recent addition to the list of C languages and AOP is arachne ...  
  http://www.emn.fr/x-info/arachne/


There are also people in belgium that have worked on legacy code and AOP, 
the legacy software was implemented in C and Cobol. 

( I cannot get to their web page it gives me a 404 ... but I found this web 
page instead of the belgian symposium on Software restructuring.) 

  http://www.info.ucl.ac.be/ingidocs/people/km/FRFC/workshop_january_2005.html#presentations

The first 2 presenters are the ones I am talking about, without wanting to 
take away the spot light from the rest of the people in that workshop. 

These are the ones that I am aware of :) 

-- Theo

PS. From all the down pages, I am either on a bad connection or my morning 
started and continues going realy bad (hahahah)





On Wed, Feb 09, 2005 at 10:24:44AM -0500, Matthias Felleisen wrote:
> Karl, Mitch, and Felix, but everyone else, too:
> 
> Felix and Mitch and I had a conversation about the need of engineers to 
> train their students in the maintenance of legacy systems, usually 
> written in C.
> 
> Larry and I had a conversation with the engineering school about the 
> same topic.
> 
> In a recent exchange with Karl, I came across this statement:
> 
> >The empirical hypothesis beneath AOP is  that these constructs enable 
> >the effective modularization of crosscutting concerns. The  ability to 
> >pattern match across an entire code base, and to extend and modify it 
> >in ways  that are not possible with inheritance is at the heart of the 
> >matter.
> 
> If this is true and AOP is also about change huge code bases to do the 
> right thing _after the fact_, then has anyone thought of developing an 
> AOP system for C so that engineers can re-engineer concerns in piles of 
> C code and help programmers navigate ill-defined, useful, and 
> to-be-maintained systems? If not, why is nobody working on this? Is CS 
> really guilty of always solving engineering problems that nobody has 
> created yet?
> 
> -- Matthias
> 
> 
> _______________________________________________
> PRL mailing list
> PRL at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/prl