ACM Home Page
Please provide us with feedback. Feedback
Minimizing ripple recompilation in a persistent software environment
Full text PdfPdf (803 KB)
Source ACM Annual Computer Science Conference archive
Proceedings of the 1990 ACM annual conference on Cooperation table of contents
Washington, D.C., United States
Pages: 166 - 172  
Year of Publication: 1990
ISBN:0-89791-348-5
Authors
M. Kazerooni-Zand  Department of Computer Science, Langston University, Langston, Oklahoma
M. H. Samadzadeh  Department of Computing Information Science, Oklahoma State University, Stillwater, Oklahoma
K. M. George  Department of Computing Information Science, Oklahoma State University, Stillwater, Oklahoma
Sponsor
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 1,   Downloads (12 Months): 8,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/100348.100374
What is a DOI?

ABSTRACT

The ripple recompilation problem is caused by modifying one or more modules in an integrated set of modules, or it results from forming a new integrated set of modules. This problem could be significant if the modified modules are widely used in the set. The main objective of this paper is to present the systematic and efficient technique employed in ROPCO (Reuse On Persistent Code and Object code) to limit this effect in a persistent reuse environment. The problem is addressed in the context of strongly-typed and separately-compiled programming languages. The approach presented consists of two phases. In the first phase, the compilation dependency graph of all modules is generated, change sets are computed, and candidate modules are marked. In the second phase, modules that are candidates for recompilation are visited and two lists for logical and physical inconsistencies are generated. Algorithms are given for both phases. An analysis of the computational complexity of the algorithms is also included.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
AH83
 
AS86
BR82
HK86
 
KF89
M. Kazerooni-Zand and D. D. Fisher, "Deletion on Persistent B-trees," Proc. Workshop on Applied Computing '89, ACM, Oklahoma, 90-96 (1989).
 
KG89
M. Kazerooni-Zand, M. H. Samadzadeh, and K. M. George,"ROPCO: Art Environment for Micro-lncremental Reuse," To be appear in Proceedings of IEEE International Phoenix Conference on Computer and Communications, Arizona, March (1990).
 
MM76
M. D. Mcllory, "Mass-Produced Software Component," Software Engineering Concepts and Techniques, Petrocelli/Charter, Brussels, Belgium, 88-98 (1976).
RC86
RP86
SK88
TB85
 
WT84
W. Teitelman, '~rhe Cedar Programming Environment: A Midterm Report and Examination," CSL-83-11, June (1984).
WT86
 
WT85


Collaborative Colleagues:
M. Kazerooni-Zand: colleagues
M. H. Samadzadeh: colleagues
K. M. George: colleagues