Re: On Legacy Applications and Previous Work

baxter@austin.sar.slb.com (Ira Baxter) writes:
>[One model of resue...]


For another intriguing view on code reuse see Gregor Kiczales' work on
Open Implementations.


%A Gregor Kiczales
%T Towards a New Model of Abstraction in Software Engineering
%J Proceedings of the International Workshop on Reflection and
Meta-Level Architecture
%D November 1992
%C Tokyo, Japan
%E Akinori Yonezawa
%E Brian Cantwell Smith
%P 1-11


One important lesson here is that implementations typically "lock down"
performance decisions. For example, the implementor uses an array lookup
instead of a <value, pair> list because an array is good for the expected
case dense values. However, clients that have sparse values will pay for
the array implementation with big memory allocations and poor reference
locality. These decisions thus mean that various acceptable *interfaces*
have inadequate performance and that eventually limits the code's
reusability.


;-D on ( Legendary applications ) Pardo
--

Return to the comp.compilers page.
Search the comp.compilers archives again.