From b3121747854cceb4e9bbd922b9da262110143540 Mon Sep 17 00:00:00 2001 From: Jason Self Date: Tue, 19 Dec 2017 10:57:44 -0800 Subject: [PATCH] Abstract: Remove duplicate reference to the Muddle name in parentheses --- md/language.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/md/language.md b/md/language.md index fe739e6..8ac503e 100644 --- a/md/language.md +++ b/md/language.md @@ -19,21 +19,21 @@ This document is free of known copyright restrictions. Abstract ======== -The Muddle programming language began existence in late 1970 (under -the name Muddle) as a successor to Lisp (Moon, 1974), a candidate -vehicle for the Dynamic Modeling System, and a possible base for -implementation of Planner (Hewitt, 1969). The original design goals -included an interactive integrated environment for programming, -debugging, loading, and editing: ease in learning and use; facilities -for structured, modular, shared programs; extensibility of syntax, -data types and operators: data-type checking for debugging and -optional data-type declarations for compiled efficiency; associative -storage, coroutining, and graphics. Along the way to reaching those -goals, it developed flexible input/output (including the ARPA -Network), and flexible interrupt and signal handling. It now serves as -a base for software prototyping, research, development, education, and -implementation of the majority of programs at MIT-DMS: a library of -sharable modules, a coherent user interface, special research +The Muddle programming language began existence in late 1970 as a +successor to Lisp (Moon, 1974), a candidate vehicle for the Dynamic +Modeling System, and a possible base for implementation of Planner +(Hewitt, 1969). The original design goals included an interactive +integrated environment for programming, debugging, loading, and +editing: ease in learning and use; facilities for structured, +modular, shared programs; extensibility of syntax, data types and +operators: data-type checking for debugging and optional data-type +declarations for compiled efficiency; associative storage, +coroutining, and graphics. Along the way to reaching those goals, it +developed flexible input/output (including the ARPA Network), and +flexible interrupt and signal handling. It now serves as a base for +software prototyping, research, development, education, and +implementation of the majority of programs at MIT-DMS: a library of +sharable modules, a coherent user interface, special research projects, autonomous daemons, etc. This document was originally intended to be a simple low-level -- 2.31.1