Building A Family of Compilers

Authors

  • Pooja Gulia Department of Computer Science and Engineering, Dronacharya College of Engineering, Affiliated to Maharishi Dayanand University, Rohtak, Haryana, India
  • Simran Bhatti Department of Computer Science and Engineering, Dronacharya College of Engineering, Affiliated to Maharishi Dayanand University, Rohtak, Haryana, India
  • Vandana Tayal Department of Computer Science and Engineering, Dronacharya College of Engineering, Affiliated to Maharishi Dayanand University, Rohtak, Haryana, India

DOI:

https://doi.org/10.37591/rtpl.v2i2.412

Keywords:

Compiler, programming language, paradigm

Abstract

The name "Compiler" is primarily used for programs that translate source code from a high-level programming language to a lower level language. We have developed and maintained a set of closelyrelated compilers. Although, much of their code is duplicated and shared, they have been maintainedseparately because they are treated as different compilers. We present a perspective on the past contributions, current status, and future directions of compiler technology and make four main recommendations in support of a vibrant compiler field in the years tocome.Even if, they were merged together, the combined code would become too complicated to serve as the base for another extension. We describe our experience to address this problem by adopting the product line engineering paradigm to build a family of compilers. This paradigm encourages developers to focus on developing a set of compilers rather than ondeveloping one particular compiler.

 

Cite this Article
Gulia Pooja, Bhatti Simran, Tayal Vandana. Building A Family of Compilers. Recent Trends in Programming Languages. 2015; 2(2): 25–29p.

 

References

Blume et al. Exception handlers as extensible cases. University of Chicago, CS Technical Report.

Kio KC, Taejon L, Patrick D. Feature-Oriented Product Line Engineering. IEEE Software. 2002; 4: 58–65p.

L. Kwan woo , K. C. Kio, L. Taejon. XXX Concepts and Guidelines of Feature Modeling for Product Line Software Engineering.

SEI. http://www.sei.cmu.edu/productlines/

Simon Peyton Jones. Norman Ramsey and Fermín Reign. C–: A Portable Assembly Language that Supports Garbage Collection. PPDP.

F. Karl, B. Moshe. Open Source Development with CVS. 1999.

Ben et al. Version Control with Subversion, O’Reilly Media. 2004.

Appel, Andrew W., David B. MacQueen. Standard ML of New Jersey. In: Programming Language Implementation and Logic Programming, 1–13p. Springer Berlin Heidelberg, 1991.

Stallman, Richard. Using and porting the GNU compiler collection. In: MIT Artificial Intelligence Laboratory. 2001. The GNU Compiler Collection.

David PL. On the Design and Development of Program Families. IEEE Transactions on Software Engineering . 1976.

David PL. Designing Software for Ease of Extension and Contraction. IEEE Transactions on 1. 1976: 1–9p.

David G., Mary Shaw. An Introduction to Software Architecture.1994.

Robert H. Programming in Standard ML. Carnegie Mellon University. Working draft. 1997.

Larry PC. ML for the Working Programmer. Cambridge University Press. 1996.

Czarnecki and Eisenecker. Generative Programming-Methods, Tools, and Applications, Addison-Wesley. 2000.

A. Robert, G. David. Formalizing Architectural Connection. IEEE Computer Society Press. 1994.

Downloads

Published

2016-01-07

Issue

Vol. 2 No. 2 (2015)

Section

Research Articles

License

Declaration and Copyright Transfer Form

(to be completed by authors)

I/ We, the undersigned author(s) of the submitted manuscript, hereby declare, that the above manuscript which is submitted for publication in the STM Journals(s), is not published already in part or whole (except in the form of abstract) in any journal or magazine for private or public circulation, and, is not under consideration of publication elsewhere.

  • I/We will not withdraw the manuscript after 1 week of submission as I have read the Author Guidelines and will adhere to the guidelines.
  • I/We Author(s ) have niether given nor will give this manuscript elsewhere for publishing after submitting in STM Journal(s).
  • I/ We have read the original version of the manuscript and am/ are responsible for the thought contents embodied in it. The work dealt in the manuscript is my/ our own, and my/ our individual contribution to this work is significant enough to qualify for authorship.
  •  I/We also agree to the authorship of the article in the following order:

Author’s name                                    

 

1. ________________

2. ________________

3. ________________

4. ________________

 

We  Author(s) tick this box and would request you to consider it as our signature as we agree to the terms of this Copyright Notice, which will apply to this submission if and when it is published by this journal.