PLANNER-73(ID:3346/pla015)Interim name for PLASMA Related languages
References: in [ACM SIGACT-SIGPLAN] Proceedings of the ACM Symposium on Principles of Programming Languages, Boston, October 1973. Association for Computing Machinery. view details The PLANNER concept was developed by Hewitt at MIT starting in 1967 (Hewitt 1971, 197Z), and Sussman and Winograd built a first implementation, MICRO-PLANNER, which contained a subset of PLANNER features. These projects established the basis of the currently popular concept of procedural representation of knowledge. CONNIVER is a recent attempt by Sussman at MIT to remedy some observed shortcomings in the practical use of PLANNER, while preserving its good ideas. in [ACM] ACM Computing Surveys (CSUR) 6(3) September 1974 view details in [ACM] ACM Computing Surveys (CSUR) 6(3) September 1974 view details in [ACM] ACM Computing Surveys (CSUR) 6(3) September 1974 view details in [ACM SIGACT-SIGPLAN] Proceedings of the 2nd ACM SIGACT-SIGPLAN Annual Symposium on Principles of Programming Languages 1975, Palo Alto, California view details in [ACM SIGACT-SIGPLAN] Proceedings of the 2nd ACM SIGACT-SIGPLAN Annual Symposium on Principles of Programming Languages 1975, Palo Alto, California view details in [ACM SIGACT-SIGPLAN] Proceedings of the 4th ACM SIGACT-SIGPLAN Annual Symposium on Principles of Programming Languages January 1977 view details This paper describes Cola, an object oriented command language for Hydra; Hydra is a capability-based operating system that runs on C.mmp, a tightly coupled multiprocessor. The two primary aspects of Cola, that it is a command language for Hydra, and that it is based on the object paradigm, are examined. Cola was designed to effect a correspondence between capabilities in Hydra and objects that are supported by the language. Cola is based on Smantalk in that it uses message-passing as a control structure to allow syntactic freedom in the expression of commands to the system. Cola objects are arranged in a hierarchy, and the message-passing mechanism was designed to exploit this structure by automatically forwarding an unanswered message up the hierarchy. Two ramifications of this mechanism, automatic inheritance and shadowing, are discussed. An evaluation of the design decisions is also given in [ACM SIGACT-SIGPLAN] Proceedings of the 4th ACM SIGACT-SIGPLAN Annual Symposium on Principles of Programming Languages January 1977 view details |