[PRL] legacy code and AOP

[Mitchell Wand]

> 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?

I don't know about C -- surely the model-checking folks at Berkeley et
al have been pawing over C code bases for years, but that's not AOP.

As I understand it, Filman & Havelund have been doing something like
this for the existing NASA codebases in Java.

--Mitch