Planner (programming language)

Planner (programming language)
Name	Planner
Paradigm	Logic programming, procedural programming, mixed-paradigm
Designer	Carl Hewitt, John McCarthy (influences), Gerald Sussman (associated)
First appeared	1971
Typing	dynamic
Implementations	e.g., Micro-Planner, Pop-11-based systems
Influenced by	Lisp, McCarthy's research, Lambda calculus
Influenced	Prolog, Actor model, AI languages

Planner (programming language) is an early mixed-paradigm programming language developed in the late 1960s and early 1970s that combined procedural control with declarative pattern-directed invocation. Originating in academic settings, it contributed ideas to automated reasoning, artificial intelligence, and concurrent computation. Planner's design intersected with multiple research threads at institutions and projects that shaped modern programming languages and computational theories.

History and Development

Planner emerged from research environments associated with institutions such as Massachusetts Institute of Technology, Stanford University, Carnegie Mellon University, and the RAND Corporation where researchers like Carl Hewitt worked alongside figures tied to the Artificial Intelligence Laboratory, MIT, Project MAC, and researchers influenced by John McCarthy. Development occurred alongside contemporaneous initiatives such as the LISP community, the Stanford AI Laboratory (SAIL), and government-funded programs like those sponsored by the Advanced Research Projects Agency that connected to the ARPA network. Conferences and workshops including meetings of the Association for Computing Machinery and the International Joint Conference on Artificial Intelligence provided venues where Planner concepts were discussed alongside work from scholars active at Bell Labs, Bolt Beranek and Newman, and the University of Edinburgh. The language's timeline overlapped with milestones such as the standardization efforts around ALGOL, the creation of Pascal by Niklaus Wirth, and the rise of languages like SIMULA that influenced object and process modeling.

Language Design and Features

Planner's core idea combined procedural invocation mechanisms with pattern-directed assertion and goal-reduction strategies, drawing inspiration from earlier systems like LISP and theoretical work from people associated with John McCarthy and Alan Turing's computational concepts. It introduced explicit constructs for rule-based control, backtracking management, and metacircular evaluation similar to approaches later seen in Prolog and rule engines used in projects at Xerox PARC and SRI International. Planner incorporated mechanisms for assertion, retraction, and guarded invocation, aligning it with research strands pursued at MIT Artificial Intelligence Laboratory, University of California, Berkeley, and Carnegie Mellon University's robotics and reasoning groups. The language supported dynamic data structures and runtime code modification, features that resonated with work at Stanford Research Institute and influenced later systems in both academic and industrial settings, including developments connected to AI Winter-era toolkits.

Syntax and Semantics

Planner's syntax reflected hybrid influences from LISP parenthetical notation and early procedural languages like ALGOL 60 and BCPL. Semantic design emphasized pattern matching, goal reduction, and control constructs for exceptions and backtracking; these semantics paralleled investigations into non-determinism occurring in research circles involving John Backus and theorists studying the Lambda calculus and formal semantics at institutions such as Princeton University and University of Cambridge. Planner's operational semantics defined how assertions interacted with procedural rules and how directed invocation resolved goals, ideas that later found formal expression in proof theory and logic programming frameworks discussed at venues like the International Conference on Logic Programming and in publications by researchers affiliated with University of Edinburgh and University of Oxford.

Implementation and Implementations

Multiple implementations and experimental systems implemented Planner concepts, including Micro-Planner and derivative systems used in academic projects at MIT, Stanford, and Carnegie Mellon University. Implementations were often prototypes running on architectures like the DEC PDP-10, Xerox Alto, and machines used in Project MAC and in industrial labs such as Bell Labs. Implementers interacted with toolchains and environments from groups at Digital Equipment Corporation and research platforms developed at RAND Corporation. Implementations influenced or interoperated with environments maintained at places like Xerox PARC, SRI International, and university research clusters where languages such as Scheme and early ML were also evolving.

Influence and Legacy

Planner's influence is visible in later logic and rule-based languages such as Prolog, in the Actor model research promoted by Carl Hewitt that affected concurrent computation discussions at MIT and Carnegie Mellon University, and in production rule systems developed in industry settings like Siemens and IBM Research. Its ideas echoed through work at Xerox PARC on intelligent agents, into academic curricula at Stanford and MIT, and into theoretical treatments found in conferences hosted by the Association for Computational Linguistics and the International Joint Conference on Artificial Intelligence. Planner informed research in knowledge representation practiced at SRI International and influenced language design conversations at institutions such as University of California, Berkeley and University of Toronto. Elements of Planner's control constructs and pattern-directed invocation persisted in later systems developed at Bell Labs and in AI projects sponsored by DARPA.

Examples and Use Cases

Planner was used in experimental artificial intelligence projects, automated theorem proving prototypes, and early natural language understanding systems developed in labs at MIT, Stanford, and Carnegie Mellon University. Practical demonstrations included rule-based control for robotics research linked to Stanford Research Institute initiatives, and prototype expert systems explored at SRI International and industrial research groups such as IBM Research. Educational use occurred in courses at Massachusetts Institute of Technology and Stanford where students compared Planner with LISP and contemporaneous languages like Prolog and Scheme; its patterns influenced demonstration systems presented at venues like the International Joint Conference on Artificial Intelligence.

Criticism and Limitations

Critics highlighted Planner's complexity relative to more specialized languages, pointing to challenges documented in discussions at meetings of the Association for Computing Machinery and critiques by researchers from Bell Labs and Xerox PARC. Performance and scalability issues arose on hardware such as the DEC PDP-10 and early workstations, drawing comparisons with more optimized systems developed at IBM Research and in commercial environments. Debates over semantics and formal reasoning involved contributors from Princeton University, University of Cambridge, and University of Edinburgh who contrasted Planner's procedural/declarative mix with the purity sought in Lambda calculus-inspired languages and typed systems like ML.

Category:Programming languages