Added SHRDLU and MicroPlanner.

Makefile

@@ -56,7 +56,7 @@ DOC = info _info_ sysdoc sysnet syshst kshack _teco_ emacs emacs1 c kcc \
       aplogo _temp_ pdp11 chsncp cbf rug bawden llogo eak clib teach pcnet \
       combat pdl minits mits_s chaos hal -pics- imlac maint cent ksc klh \
       digest prs decus bsg madman hur lmdoc rrs danny netwrk klotz hello \
-      clu r mini nova sits jay rjl nlogo mprog2 mudbug cfs hudini
+      clu r mini nova sits jay rjl nlogo mprog2 mudbug cfs hudini shrdlu
 BIN = sys sys1 sys2 emacs _teco_ lisp liblsp alan sail comlap \
       c decsys graphs draw datdrw fonts fonts1 fonts2 games macsym \
       maint _www_ gt40 llogo bawden sysbin -pics- lmman shrdlu imlac \

build/build.tcl

@@ -180,6 +180,7 @@ if {$env(BASICS)!="yes"} {
     source $build/zork.tcl
     source $build/sail.tcl
     source $build/typeset.tcl
+    source $build/shrdlu.tcl
 }
 
 bootable_tapes

build/shrdlu.tcl

@@ -0,0 +1,26 @@
+log_progress "ENTERING BUILD SCRIPT: SHRDLU"
+
+respond "*" ":cwd shrdlu\r"
+
+respond "*" ":complr\r"
+respond "_" "shrdlu; graphf\r"
+respond "_" "\032"
+type ":kill\r"
+
+respond "*" ":lisp\r"
+respond "Alloc?" "n"
+respond "*" "(load 'loader)"
+respond "T" "(loadshrdlu)"
+respond "|CONSTRUCTION COMPLETED|" "(dump-it)"
+respond "*" ":pdump shrdlu;ts shrdlu\r"
+respond "*" ":kill\r"
+
+respond "*" ":lisp\r"
+respond "Alloc?" "n"
+respond "*" "(load 'loader)"
+respond "T" "(load 'plnrfi)"
+respond "T" "(loadplanner)"
+respond "(THERT TOP LEVEL))" "(dump-planner)"
+respond "*" ":pdump shrdlu;ts plnr\r"
+respond "*" ":kill\r"
+

build/timestamps.txt

@@ -2623,8 +2623,35 @@ share/plot2.usage 198108141042.19
 share/plot3d.66 198307070939.36
 share/print.33 198307070938.51
 share/tekplt.171 198307151358.48
-shrdlu/demo.flick 197110311951.55
+shrdlu/_index.4 197406260803.33
+shrdlu/blockl.4 197412031831.29
+shrdlu/blockp.3 197611210203.25
+shrdlu/blocks.144 197404141658.14
+shrdlu/data.6 1976111210318.42
+shrdlu/demo.flick 197112020051.55
+shrdlu/diction.73 197305082237.12
+shrdlu/ginter.5  197405071047.29
+shrdlu/gramar.28 197506021125.06
+shrdlu/graphf.3 
+shrdlu/loader.18 197502061940.06
+shrdlu/help.doc 197302121331.57
+shrdlu/mannew.2 197404211340.30
+shrdlu/manual.1 197210170841.38
+shrdlu/manual.cmu 197210170841.38
+shrdlu/minih.doc 197302121331.41
+shrdlu/morpho.13 197701311810.50
+shrdlu/newans.78 197412032331.01
+shrdlu/plnr.182 197412122015.16
+shrdlu/progmr.57 197507021825.29
+shrdlu/setup.62 197412031832.50
+shrdlu/show.13 197412031822.58
+shrdlu/smass.19 197411031026.51
+shrdlu/smspec.94 197412031825.04
+shrdlu/smutil.148 197412032310.43
+shrdlu/syscom.180 197701311806.41
+shrdlu/thtrac.22 197309301841.37
 shrdlu/ts.twdemo 197110311544.38
+shrdlu/twutil.14 197303162142.26
 sits/-read-.-this- 197503032229.00
 sits/bigf.7 197703090139.50
 sits/bigf.ast 197507300444.54

doc/shrdlu/mannew.2

@@ -0,0 +1,60 @@
+     On the A.I. machine, a reasonably fluent
+and debuged version of SHRDLU is alway availlable as
+SHRDLU > DSK SHRDLU and can be run as a job
+by typing SHRDLU<cntrl. k> at DDT. This version is
+in interpreted with
+all its options including a grind and trace. Consequently
+it occupies arround 200k of core (caution: indiscriminately
+running a job that big in the middle of the day is a 
+good way to make enemies!!!!! Alway check the level
+of system usage befoere loading.
+.sp 1
+     The first sign of life from SHRDLU looks
+like this:
+          SHRDLU version 101   created on 4-27-73
+           type <space> to go to "ready" state, type "?" for help
+          >>>
+.sp 1
+     The version number has certain accessable 
+information associated with it describing the actual
+files used in this version and any phenomena peculiar to it.
+the prompt characters ">>>" are produced by the system's
+handcrafted real-eval-print loop. When this has
+been printed you are boht talking to LISP where you can do any
+of the normal things (check values of bound variables, evaluate functions.
+etc.) and you can use the SHOW-TELL mechanism which is designed
+as a convenient way to fiddle with SHRDLU's knobs & switches,
+define new wiords, examine sturctures as they are set up, etc.
+More about it later.
+     SHRDLU is dumped with all its display options turned
+off so that the initial command state is a reasionable place to
+set the parameters the way you want them before running any 
+sentences. All the options will be described in the next
+section. 
+.sp 1
+     Moving from this state to the one where
+SHRDLU accepts sentences is doen by typing
+"t " (the letter "t" followed by a space). The responce
+will be:
+          READY <cr>
+     At this point you can type in a sentence and
+it will be interpreted and responded to. Mistyped
+letters within a word can bve erased
+by typing a <rubout> in the usua; manner and unintended
+words can be removed by typing a <rubout> agter an 
+intervening break character (comma or space usualy). As soon
+as the sentence terminating punctuation (. ? !) has been
+typed, the sentence is automaticly processed and unless
+some display options have been turned on, (or you stumbled across a bug !!)
+the next thing that you see will be the 
+responce to what you typed in from SHRDLU.A switch can be set (see the next section)
+to cause a break at this point (immediately
+after a response) and
+permit the examination of the various structures that were added to the program's
+memory for example. Without the break (or after it has been dismissed 
+we get another "READY" and can continue as before.
+     The break-loop (otherwise known as "command state")
+can be entered fron the "ready state" by typing <altmode><altmode>
+instead of stsrting a sentence. Exiting from it will result
+in another "READY".
+