
2/10/94:

This is the PC-Scheme version of McDypar.  It must be run under DOS (the
files have already been converted to DOS style).  It has been tested and
should work under PC-Scheme (pcs) under DOS.

To use, I suggest copying all of the mcdypar files  into your own mcdypar
directory in your own home directory.  To run, enter PC-Scheme from DOS
by using the command:

DOS-PROMPT] pcs

This will start up PC-Scheme.  From there, enter:

(load "init.s")

It should take a minute or so to load in all of the different mcdypar files.
Parsing an example in the PC-Scheme version of mcdypar is done using the
"parse" command (defined in toplevel.s).

For example:

> (parse '(john picked up the ball.))

It should trace out the demons and major functions it is using, and end by
printing out the CD parse of the story.

The file "trace.s" controls what is displayed as the parse goes on.  For
example, to stop mcdypar from tracing most of the major functions (e.g.
split-config, split-rest), change the (define ^bob t) to (define ^bot nil),
or just set ^bob to nil while any time after loading init.s.  (Note that I
am *not* responsible for having written this program and its awful choice
of global variables and general scheme style! -- Trent)

The most complex example the example lexicon (lexicon.s) and demons
(dm_defs.s) provided can handle is:

> (parse '(john picked up the ball and dropped it in the box.))

To see what happens when something doesn't match the lexicon and demons,
do a few tests yourself to see what it returns.  Some examples you might try:

> (parse '(the ball picked up John))
> (parse '(dropped the ball))
> (parse '(john hit the ball))

To extend the lexicon and demons, make your own separate lexicon and demon
files (e.g. mylex.s and mydemons.s).  Don't add them to the mcdypar files
themselves, just in case there are future bug fixes.

Good luck!

- Trent
