|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| W.G. Griswold, "Comments on "Language Design for Program Manipulation"," IEEE Transactions on Software Engineering, vol. 20, no. 3, pp. 218-219, March, 1994. | |||
| BibTex | x | ||
| @article{ 10.1109/32.268924, author = {W.G. Griswold}, title = {Comments on "Language Design for Program Manipulation"}, journal ={IEEE Transactions on Software Engineering}, volume = {20}, number = {3}, issn = {0098-5589}, year = {1994}, pages = {218-219}, doi = {http://doi.ieeecomputersociety.org/10.1109/32.268924}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Software Engineering TI - Comments on "Language Design for Program Manipulation" IS - 3 SN - 0098-5589 SP218 EP219 EPD - 218-219 A1 - W.G. Griswold, PY - 1994 KW - object-oriented languages; programming; programming theory; language design; program manipulation; design principles; object-oriented language; new programming languages; procedural language; syntax; semantics VL - 20 JA - IEEE Transactions on Software Engineering ER - | |||
The paper by E.A.T. Merks et al. "Language design for program manipulation" identifies design principles for a procedural or object-oriented language whose programs will be easier to manipulate. However, it neglects to relate these design principles to existing, broader, design principles, and in some instances omits good examples of languages meeting their criteria. The author relates the new principles to more fundamental design principles, and provides the needed examples of languages meeting their criteria. Together these additions can better help designers of new programming languages that are amenable to manipulation.
[1] E. A. T. Merks, J. M. Dyck, and R. D. Cameron, "Language design for program manipulation,"IEEE Trans. Software Eng., vol. 18, pp. 19-32, Jan. 1992.
[2] W. G. Griswold, "Program Restructuring to Aid Software Maintenance," Ph.D. thesis, Univ. of Washington, Dept. of Comput. Sci.&Eng., Aug. 1991. (Tech. Rep. 91-08-04.)
[3] W. G. Griswold and D. Notkin, "Automated assistance for program restructuring,"ACM Trans. Software Eng. Methodol., vol. 2, pp. 228-269, July 1993.
[4] E. A. T. Merks, "Acer: manipulation principles applied to language design," Ph.D. degree work in progress, School of Comput. Sci., Simon Fraser Univ., Burnaby, BC, Can.
[5] B. J. MacLennan,Principles of Programming Languages: Design, Evaluation, and Implementation, 2nd ed. New York: Holt, Rinehart, and Winston, 1987.
[6] G. L. Steele Jr.,Common Lisp: The Language (Second Edition). Burlington, MA: Digital Press, 1990.
[7] R. K. Dybvig,The Scheme Programming Language. Englewood Cliffs, NJ: Prentice-Hall, 1987.
[8] S. Horowitz, J. Prins, and T. Reps, "Integrating non-interfering versions of programs,"Trans. Program. Lang. Syst., vol. 11, no. 3, pp. 345-387, July 1989.
[9] B. Stroustrup,The C++ Programming Language. Reading MA: Addison-Wesley, 1987.
[10] U.S. Department of Defense,Reference Manual for the Ada Programming Language, Feb. 1983. ANSI/MIL-STD-1815A-1983.
[11] B. Meyers,Object Oriented Software Construction. Englewood Cliffs, NJ: Prentice-Hall, 1988.

