Towards monolingual programming environments

ABSTRACT

Most programming environments are much too complex. One way of simplifying them is to reduce the number of mode-dependent languages the user has to be familiar with. As a first step towards this end, the feasibility of unified command/programming/debugging languages, and the concepts on which such languages have to be based, are investigated. The unification process is accomplished in two phases. First, a unified command/programming framework is defined and, second, this framework is extended by adding an integrated debugging capability to it. Strict rules are laid down by which to judge language concepts presenting themselves as candidates for inclusion in the framework during each phase. On the basis of these rules many of the language design questions that have hitherto been resolved this way or that, depending on the taste of the designer, lose their vagueness and can be decided in an unambiguous manner.

REFERENCES

• 1: ANSI. The Programming Language ADA. Re{erence Manual. Lecture Notes in Computer Science,Vol. 155, ANSI/MIL-STD-1815A-1983, Springer Verlag, Berlin, 1983.
• 2: BISHOP, P.B. Computer systems with a very large address space and garbage collection. Thesis. Rep. MIT/LCS/TR-178, MIT Laboratory for Computer Science, MIT, Cambridge, Mass., 1977.
• 3: David R. Barstow , Howard E. Shrobe , Erik Sandewall, Interactive Programming Environments, McGraw-Hill, Inc., New York, NY, 1984
• 4: BOURNE, S.R. An introduction to the UNIX shell. In UNIX Programmer's Manual, vol. 2A, 7th ed., Bell Telephone Laboratories, Murray Hill, N.J., Jan. 1979.
• 5: BOUTE, R.T. Building a uniform programming environment based on data abstraction. In Proceedings of the International Computing Symposium (ICS81). ACM, New York, 1981, 415- 424.
• 6: BURROUGHS. B7000/B6000 Series Work Flow Language Reference Manual. Burroughs Co., Pub. No. 500155, 1977.
• 7: DAVIS, R., AND KING, J. An overview of production systems. In Machine Intelligence 8, E. W. Elcock, D. Michie, Eds., Ellis Horwood, Chicester, Sussex, 1977, 300-332.
• 8: Robert B. K. Dewar, Indirect threaded code, Communications of the ACM, v.18 n.6, p.330-331, June 1975 [doi>10.1145/360825.360849]
• 9: FELDMAN, S.I. Make--a program for maintaining computer programs. In UNIX Programmer's Manual, vol. 2A, 7th ed., Bell Telephone Laboratories, Murray Hill, N.J., Jan. 1979.
• 10: GOLDBERG, A., AND ROBSON, D. SMALLTALK-80. 4 vols., Addison-Wesley, Reading, Mass., 1983-1984.
• 11: GOODWIN, J.W. Why programming environments need dynamic data types. In {3}, 414-425.
• 12: GRISHMAN, R. Criteria for a debugging language. In Debugging Techniques in Large Scale Systems, R. Rustin, Ed., Courant Computer Science Symposium 1, Prentice-Hall, Englewood Cliffs, N.J., 1971, 57-75.
• 13: Ralph E Griswold, The SNOBOL 4 programming language, Prentice-Hall, Inc., Upper Saddle River, NJ, 1971
• 14: GRUENBERGER, F.J. The history of the JOHNNIAC. Ann. History Comput. 1, 1 (July 1979), 49-64.
• 15: HANSON, D.R. Variable associations in SNOBOL4. Softw. Pract. Exper. 6 (1976), 245-254.
• 16: HANSON, D.R. Event associations in SNOBOL4 for program debugging. Softw. Pract. Exper. 8 (1978), 115-129.
• 17: IBM. OS/VS2 TSO Command Language Reference. IBM Corp., Pub. No. GC28-0646-4, 5th ed., June 1978.
• 18: Kathleen Jensen , Niklaus Wirth, Pascal-User Manual and Report, Springer-Verlag New York, Inc., Secaucus, NJ, 1975
• 19: JONES, A.K. The narrowing gap between language systems and operating systems. In Proceedings IFIP Congress 77, North-Holland, Amsterdam, 1977, 869-873.
• 20: JOY, W. An introduction to the C shell. In UNIX Programmer's Manual, vol. 2C, part 1; Virtual VAX-11 Version. Computer Systems Research Group, Dept. of Electrical Engineering and Computer Science, Univ. of California at Berkeley, Aug. 1983.
• 21: Paul Klint, An overview of the SUMMER programming language, Proceedings of the 7th ACM SIGPLAN-SIGACT symposium on Principles of programming languages, p.47-55, January 28-30, 1980, Las Vegas, Nevada [doi>10.1145/567446.567451]
• 22: KLINT, P. Interpretation techniques. Softw. Pract. Exper. 11 (1981), 963-973.
• 23: Lambert Meertens, Incremental polymorphic type checking in B, Proceedings of the 10th ACM SIGACT-SIGPLAN symposium on Principles of programming languages, p.265-275, January 24-26, 1983, Austin, Texas [doi>10.1145/567067.567092]
• 24: MEERTENS, L. G. L. T., AND PEMBERTON, S. An implementation of the B programming language. Rep. CS-N8406, Centre for Mathematics and Computer Science, Amsterdam, June 1984.
• 25: MILNER, R. A theory of type polymorphism in programming. J. Comput. Syst. Sci. 17 (1978), 348-375.
• 26: Eugene W. Myers, Efficient applicative data types, Proceedings of the 11th ACM SIGACT-SIGPLAN symposium on Principles of programming languages, p.66-75, January 15-18, 1984, Salt Lake City, Utah, United States [doi>10.1145/800017.800517]
• 27: B. Randell, System structure for software fault tolerance, Proceedings of the international conference on Reliable software, p.437-449, April 21-23, 1975, Los Angeles, California
• 28: SHAW, J.C. JOSS: A designer's view of an experimental on-line computing system. In AFIPS Conference Proceedings, vol. 26, 1964 Fall Joint Computer Conference, Spartan Books, Baltimore, Md., 1964, 455-464.
• 29: Norihisa Suzuki, Inferring types in Smalltalk, Proceedings of the 8th ACM SIGPLAN-SIGACT symposium on Principles of programming languages, p.187-199, January 26-28, 1981, Williamsburg, Virginia [doi>10.1145/567532.567553]
• 30: TEITELMAN, W. INTERLISP Reference Manual. XEROX Co., Palo Alto Research Center, Palo Alto, Calif., 1978.
• 31: TEITELMAN, W., AND MASINTER, L. The INTERLISP programming environment. In {3}, 83- 96.

INDEX TERMS

Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications

          Nouns: INTERLISP; Smalltalk-80
      D.3.3 Language Constructs and Features
          Subjects: Data types and structures
  D.4 OPERATING SYSTEMS
      D.4.9 Systems Programs and Utilities
          Subjects: Command and control languages

General Terms:
Design, Languages