
                             CLIPS Release Notes

                     Version 5.1       October 18, 1991

   ====================================================================
   |        NOTICE OF COMPUTER PROGRAM USE RESTRICTIONS               |
   | This computer program is furnished on the condition that it be   |
   | used only in connection with the specific cooperative project,   |
   | grant or contract under which it is provided and that no further |
   | use or dissemination shall be made without prior written         |
   | permission of the NASA forwarding officer. [NASA JSC PT4]        |
   |      RESTRICTED TO USE FOR US GOVERNMENT PURPOSES ONLY!          |
   ====================================================================


This file contains any last minute information pertaining to this version of
CLIPS that was not included in the Reference Manual. It also contains
information of general use about CLIPS, such as where to report problems, how
to get CLIPS, a description of any known problems with the documentation or
program.

---INSTALLING ON AN IBM PC OR COMPATIBLE:---

If you received CLIPS on MS-DOS floppy disks, you should have received six
360K 5.25" disks, two 1.2M 5.25" disks or two 1.4MB 3.5" disks. Disk 1 contains
the installation program, this README.TXT file,  a Discrepancy Report Form (for
reporting bugs and other anomalous behavior), and a Change Request Form (for
requesting new features), and some of the compressed programs.  The other disks
contain the remainder of the compressed programs.

As mentioned above, for the IBM PC and compatible, we have added an
installation program on the diskette labeled CLIPS 5.1 Disk 1. It lets you
choose any category of files you want to copy and where you want them put on
the hard disk. In addition to that, the installation program will check to
determine if there is enough space on the hard disk for you to copy the files
you chose. Because the files on the disks are compressed, you MUST use the
installation program to decompress and install the desired files. You can
start the installation program from either the floppy or from your hard disk by
typing [FLOPPY-DISK-DRIVE-LETTER]:INSTALIT and selecting from the installation
menu.

The following is a list of choices you have for installing CLIPS on your Hard
Disk along with APPROXIMATE corresponding, UNCOMPRESSED sizes:

All of the distribution diskettes                     6,481,920 Bytes
1.  The CLIPS and CRSV executables                    2,203,648 Bytes
2.  Some CLIPS examples                                 266,240 Bytes
5.  The CLIPS source files                            2,940,928 Bytes
6.  The CRSV source files                             1,040,384 Bytes

As mentioned earlier, the first step is to invoke the INSTALIT.EXE. From then
on, simply make your selection and follow instructions. The only other
information the installation software needs from the user is the name of the
directory where you want the selection to be copied. If the directory does not
exist, the installation program creates it. WHEN YOU ARE ASKED TO ENTER THE
DIRECTORY NAME(s), YOUR INPUT SHOULD BE THE FULL PATHNAME TO THE DIRECTORY.
This directory is the base directory for all of the CLIPS distribution files.
The installation program will create subdirectories underneath this base to
hold different components of the distribution.

The files CLPDSSPD.EXE, CLPDSSZ.EXE and CLIPSDOS.RES are associated with
the DOS windowed interface for CLIPS.  See Volume III of the CLIPS Reference
Manual, Utilities and Interfaces Guide, for more details.

******************************************************************** 
              N O T I C E     P C     U S E R S

The clips.exe file is built with overlays and will run EXCRUCIATINGLY slow on
808x and 8028x based computers WITHOUT expanded or extended memory.  You can
recompile it with the supplied makefiles (explained below) without overlays
but you cannot have the object system and other features on because you will
run out of memory upon simply loading the executable.  For more information
see WARNINGS and GENERAL INFORMATION sections below.
*******************************************************************

---INSTALLING ON A MACINTOSH:---

If you received CLIPS on Macintosh floppy disks, you should have received two
800K disks. Disk 1 contains two Read Me files (one in TeachText and one in
CLIPS format), a Discrepancy Report Form (for reporting bugs and other
anomalous behavior), and a Change Request Form (for requesting new features).
In addition, Disk 1 contains a self extracting program for the CRSV source code,
CRSV and CLIPS executables and examples, and MPW and Think C project files as 
follows:

DISK 1:  Contents                             Files           Size
-----------------                             -----          -----
CRSV Source folder                              35            985K
Executables folder                              17            848K
Think C Project Files folder                     3            173K
MPW C Project Files folder                       3            148K
                                                             -----
                                                             2,154K Total

To install these files, create a folder on your hard disk where you want the
files to be placed, then double click on the icon and respond to queries as 
they appear.


Disk 2 contains a self extracting program for the CLIPS and Macintosh interface
source code.

DISK 2:  Contents                             Files           Size
-----------------                             -----          -----
Interface Source folder                         43            758K
CLIPS Source folder                            130           2700K
                                                             -----
                                                             3,458K Total

To install these files, create a folder on your hard disk where you want the 
files to be placed, then double click on the icon and respond to queries as 
they appear.

---INSTALLING ON A UNIX PLATFORM:---

The distribution tape for UNIX systems was created using tar. You can
extract the files from this tape using the following command

tar xvf <tape-device>

where <tape-device> is the name of the tape device for your machine 
(for example, /dev/rst0). The following directories will be created when 
the files are extracted from the tape.

Directory             Contents
------------          --------------------------------------
clips                 CLIPS 5.1 source and make files
xclips                XCLIPS interface source, CLIPS5.1 source and make files
color                 color utility source and make files


---INSTALLING ON A VAX/VMS PLATFORM:---

For VMS, the CLIPS distribution comes on a standard BACKUP format tape.

CLIPS.EXE and CRSV.EXE must be installed as foreign commands in order to
be executed from the VMS command-line.  To do this, add the following lines
to your LOGIN.COM:

$ CLIPS :== $<DISK>:<DIRECTORY>CLIPS.EXE
$ CRSV  :== $<DISK>:<DIRECTORY>CRSV.EXE

where <DISK> and <DIRECTORY> are the names of the disk and directory where
the executable images reside.  For example:

$ CLIPS :== $USER1$DISK:[JOEUSER.CLIPS]CLIPS.EXE

There are two DCL scripts provided for recompiling CLIPS and CRSV:
BUILDCLIPS.COM and BUILDCRSV.COM respectively.  To use these scripts, issue
the following commands at the VMS/DCL prompt:

$ @BUILDCLIPS

   or

$ @BUILDCRSV

Note that you must be in the directory where the source files for CLIPS or
CRSV reside in order to use these scripts.

HOW TO GET CLIPS
----------------
CLIPS was developed by the Software Technology Branch of the Information
System Directorate at NASA/Johnson Space Center. CLIPS is available to NASA
and USAF government organizations and their contractors by calling the STB
Products Help Desk between the hours of 8:00 AM to 4:45 PM (CST) Monday
through Friday at (713) 280-2233. Use of CLIPS is restricted as indicated in
the NOTICE at the top of this file and on each diskette. US Government
contractors should have their contract number, government monitor's name and
phone number to provide to the STB Products Help desk to obtain CLIPS. An
answering machine will take a message at other hours or when the line is
busy. You may also use our electronic bulletin board to obtain information or
leave us a message. The numbers are (713) 280-3896 and (713) 280-3892; set
your modem at 300, 1200, or 2400 baud, no parity, 8 data bits and 1 stop bit.
The bulletin board operates 24 hours a day, seven days a week except for
maintenance.

CLIPS is available outside of the NASA and USAF and their contractors through
COSMIC, the NASA software distribution center. The cost of previous versions of
CLIPS has been about $350 for both source code and MS-DOS or Macintosh
executable and $140 for the CLIPS documentation. Unlimited copies can be made 
after purchasing CLIPS through COSMIC. The same source code will run on nearly 
any machine which can support an ANSI or K&R C compiler. The COSMIC program 
number is MSC-21208. COSMIC can be contacted at:  
COSMIC, 382 E. Broad St.,  Athens, GA  30602, (404) 542-3265.

PROBLEMS INSTALLING OR USING CLIPS
----------------------------------
Users can obtain some help with CLIPS problems by calling the STB Products Help
desk. The Help desk is available between the hours of 8:00 AM to 4:45 PM (CST)
Monday through Friday at (713) 280-2233. Callers should leave a description of
their problem and a phone number and they will be contacted, usually within a
day. An answering machine will take a message at other hours or when the line
is busy. You may also use our electronic bulletin board to obtain information
or leave us a message. The numbers are (713) 280-3896 and (713) 280-3892; set
your modem at 300, 1200, or 2400 baud, no parity, 8 data bits and 1 stop bit.
The bulletin board operates 24 hours a day, seven days a week, except for
maintenance. Outside organizations should use the bug report forms included
with the CLIPS documentation to report problems with CLIPS.

WARNINGS, THINGS TO WATCH OUT FOR
---------------------------------
The following section describes common problems users have with CLIPS, or
things to be aware of when using CLIPS. If you are having unusual problems,
check this section and the next one before reporting a bug. You should also
carefully read and understand the changes from version 4.3 and 5.0 to 5.1 as 
explained in Appendix D of Volume I of the CLIPS Reference Manual. 
Capabilities and function names have been changed and may return different 
types.

1) VAX-VMS TERMINAL CONFIGURATION FOR CORRECT EMACS EDITOR USAGE:

The EMACS editor in CLIPS does not support anything beyond VT100 on VAX/VMS.
For newer terminals such as VT240, users need to set the terminal type in their
LOGIN.COM file to emulate VT100 as follows :

A) $SET TERM/DEVICE = VT100
B) From the VT240 terminal press F3 key which gets General Setup Menu.
   Move to 3rd item on the top row, i.e. VT100.
   Hit return until select VT100.
   Press F3 key to leave at VT100.

Users should do both A & B. If you don't emulate VT100, you will be continuously
kicked out of the CLIPS editor back to the VAX DCL command line at random and
you may lose your file(s).

2) Because it appears that the VAX implementation of extern does not follow
ANSI or K & R, VAX VMS will NOT link with the file edterm.obj in a library
unless you use the /include option. Or you can link directly with edterm.obj.
If you don't do this, the editor files will not get linked and yet, you will
not get link errors and your program will crash when you try to use the editor.

3) Using the integrated editor to edit large files and then execute them in
CLIPS could cause severe memory problems on a PC. The editor itself does not
take up all that much memory, but a large file of rules that is in the editor
and then loaded into CLIPS could cause the machine to do any of three things;
completely hang, exit to DOS with some kind of error message, or warn about
memory failures and refuse to compile a rule or file. The moral is when working
on a PC, use a PC with as much memory (DOS accessible, i.e. <= 640k) as 
possible, and avoid editing large files while in CLIPS. Because CLIPS accesses 
memory via DOS, it cannot use extended or expanded memory except as described 
in 11 below. The Macintosh generally does not have as severe a memory 
limitation for rules; however, the Macintosh toolbox editor cannot edit files 
larger than 32K.

4) Because of differences in machines, the allowable range of values a CLIPS
number may have can vary. Particularly, the largest or smallest allowed value
on one machine may cause floating point overflows or underflows, respectively,
on another.

5) If one uses the option "r+" to read from and write to a file, in the case
that the file does not already exist, CLIPS will not be able to find it. The
above option should only be used for files that already exist. So, if you want
to read to and write to the same file that does not necessarily exist, you
should check if it already exists and, if not, open it for writing, i.e. "w",
and close immediately prior to accessing with "r+". Also be aware that
different C compilers may implement r+ to overwrite or append to the file and
consequently your results with different compilers may vary.

6) CLIPS is ANSI C code, it is NOT C++ and will NOT compile as C++ code.
However you can use the ANSI C compiler supplied with Turbo C++ 1.0 to compile
it as ANSI C and take advantage of Borland's VROOM to use overlays.

7) While you can compile CLIPS 5.1 with all features activated on a PC, you
will find that when you attempt to run it, the program crashes out of memory.
You have several choices in this case. You can deactivate some features and
recompile. Or you can compile with the ANSI C compiler which comes with Turbo
C++ version 1.0 (as ANSI C code NOT C++) and use its VROOM technology to gain
significant room in memory; we have supplied a make file to do so, see below.
The executable for CLIPS 5.1 for IBM personal computers and compatibles which
we distribute is compiled with VROOM and all features activated. You can also 
move to another machine which can directly access more memory, such as a 
Macintosh, VAX or UNIX workstation.

8) If, on an IBM PC or compatible, you plan to use the DOS print command from
inside CLIPS be sure to load the resident portion of print BEFORE starting
CLIPS (i.e. execute print from DOS before starting CLIPS). Failure to do so
will result in memory being held and not released even after CLIPS is
terminated. The only way to release this memory is by rebooting.

9) Terminate and Stay Resident (TSR) programs under DOS will not work from
CLIPS system calls. Instead, spawn a DOS shell from CLIPS and execute the TSR
from the shell.

10) When using the CLIPS system command you may find that you get a 'normal'
return from the call but your command to the OS was not executed. This occurs
under DOS when there is not sufficient memory to spawn a DOS shell and execute
the command. Since there is no return code from DOS which indicates this
problem, there is no way for CLIPS to tell you that your command did not get
executed. Furthermore, since this problem depends on the amount of memory
present, and the amount of memory you have present varies by what programs you
have loaded, both in CLIPS and TSR's etc., the problem is often intermittent
on even your own computer. If it appears your system commands are not being
executed, check to see that you have enough free memory and, if not, then you
will have to first free up some memory.

11) BLOAD clears the environment of constructs (defrules, deffacts,
deftemplates, deffunctions) before loading a file into memory. BLOAD can be
called at any time unless some constructs that BLOAD will affect are in use
(i.e. a deffunction is currently executing). When you do a BLOAD, all operant
defrules, deffacts, deftemplates and deffunctions are deleted (but not
facts). Once a BLOAD has executed, you cannot load any constructs with LOAD
or delete any constructs. You can do another BLOAD (which will delete all
constructs from the current BLOAD); you can also clear and then use LOAD. See
Section 11.1.3 of the CLIPS Basic Programming Guide for more information. Be 
absolutely certain that when you BLOAD a file, that it was BSAVEd with the SAME
version of CLIPS. It is a serious error to BLOAD files BSAVEd with different 
versions of CLIPS; your computer may hang/crash.

12) Using expanded (EMS) or extended (XMS) memory or IBM PCs and compatibles.
We have investigated the use of both expanded and extended memory under DOS.
We feel the enormous amount of work necessary to use expanded memory cannot be
justified. We expect to begin work on a Microsoft Windows 3.0 version of
CLIPS which can use extended memory and this could alleviate memory
constraints on IBM and compatible PCs. Because CLIPS gets its memory from DOS
and DOS cannot use extended memory, there is no straightforward way for
CLIPS to use extended memory. You could buy a DOS memory extender, then
recompile and relink CLIPS with their libraries (for Microsoft C and Turbo C,
at least) to use extended memory. Normally the vendors of DOS memory extenders
may require a license agreement (and fees) of those who distribute programs
built with their memory extender libraries. For further information, please
contact the three vendors of DOS extenders we know of (they were reviewed in
April 1990 BYTE):

Ergo Computing 
One Intercontinental Way 
Peabody, MA 01960-9850 
(508) 535-7510 

Phar Lap Software 
60 Aberdeen Ave.
Cambridge, MA 02138
(617) 661-1510

Rational Systems
220 North Main St.
Natick, MA 01760
(508) 653-6006

We have also heard of DOS extenders which do not require runtime royalty fees
including Zortech C++ and Intel Codebuilder.  We have not used Intel
Codebuilder directly but have heard that it has problems with nested header
files and some real-mode interrupts, such as the clock timer.  Zortech C++
V3.00r2 is rather buggy, unfortunately, and we would recommend against
using it.

12) If you move the source code for CRSV from an IBM-PC to another 
type of computer, don't move the interface code because it won't work on 
anything but an IBM-PC. CRSV IBM-PC interface source code files begin
pc------.c or pc------.h.

13) For IBM Mainframes you should be able to compile and execute CLIPS 5.1
now. We have added a special header file, SHRTLNKN.H, to provide short name
file aliases to satisfy the linker limitation of 8 characters or less in a
file name. In addition, you MUST set the flags for GENERIC to 1 and
ANSI_COMPILER to 1. This procedure has been tested under MVS and VM.
Finally, you may want to make the following changes to the source code for IBM
C/370 Compiler and Library before compiling.

Our own limited testing on IBM mainframes and the reports of others who have
ported CLIPS to IBM mainframes have indicated that output is only flushed to
the screen when a carriage return is encountered (even an fflush call will not
flush output). The following changes can be made to the CLIPS source code to
force output to be displayed after the CLIPS prompt appears and before any
read or readline calls.

---------------------------------------------------------------------
In the PrintPrompt function in the COMMLINE.C file, change the following line

    PrintCLIPS(WCLIPS,"CLIPS> ");

TO

    PrintCLIPS(WCLIPS,"CLIPS>\n");

---------------------------------------------------------------------
In the ReadFunction function in the SYSIO.C file, change the following lines

   if (strcmp(dummyid,"stdin") == O)
      {
        inp_tkn.type = STOP;

TO

   if (strcmp(dummyid,"stdin") == O)
      {
        PrintCLIPS("stdout","\n");
        inp_tkn.type = STOP;

----------------------------------------------------------------------
In the ReadlineFunction function in the SYSIO.C file, change the following line

   buffer = FillBuffer(logicalName,&CLIPSInputCount,&line_max);

TO

   if (strcmp(logicalName,"stdin") = O) PrintCLIPS("stdout","\n");
   buffer = FillBuffer(logicalName,&CLIPSInputCount,&line_max);
----------------------------------------------------------------------

14) If you are using Think C version 5.0 on the Macintosh to compile CLIPS, be 
aware that there are known problems with almost all of the code optimization 
features in the Think C compiler. We recommend that if you use version 5.0, that
you turn off all of the optimization options. The CLIPS Macintosh distribution
executable was created using Think C 4.0, however, we were also able to 
generate an executable using Think C 5.0 (with local code optimizations
enabled)  which passed all of our validation tests. The Think C 5.0 executable
was both smaller and faster than the Think C 4.0 executable.  We have
recently tested Think C 5.0.1 (a patch available on most of the public
networks), and this version does not appear to have any of the optimizer bugs
present in Think C 5.0.

15) Formation Desktop 2.1, a windowing package from Aspen Scientific, was
used to create the windowed interface for CLIPS under DOS.  We have recently
discovered that Aspen Scientific has gone out of business.  We are currently
trying to determine if we can legally distribute our modified version of the
window library, so that users may easily recompile the interface.  For the
moment, however, Formation Desktop 2.5 can be obtained from the following
company (with no technical support):

Austin CodeWorks
11100 Leafwood Lane
Austin, Texas 78750-3409
(512) 258-0785

Further information on obtaining the source code for CLIPSDOS and recompiling
the interface can be found on page 55 of Volume III of the CLIPS Reference
Manual, the Utilities and Interfaces Guide.

KNOWN PROBLEMS WITH CLIPS
-------------------------
The following section describes any known problems with CLIPS. Where possible,
workarounds or fixes will also be described. If you discover bugs and
workarounds please call the HELP DESK and report them so we can update this
file. There is also an electronic form for reporting discrepancies 
included on the distribution disks. Thanks.

1) Many compilers provide a code optimization option. Be aware that some
compilers on occasion will incorrectly optimize code. If you encounter problems
running CLIPS and originally compiled the CLIPS source code using code 
optimization, then try recompiling CLIPS without using code optimization.

2) You cannot always break out of a while loop on IBM-PCs with 
CTRL-C but you should be able to break out on a UNIX workstation. You may be 
able to break out on an IBM-PC with CTRL-C if your program is 
performing output; you will be able to break out with CTRL-Break on an IBM-PC.

A bug in CLIPS 5.1 prevents Ctrl-C and Ctrl-Break from terminating a batch
file in the IBM-PC executables.  If you recompile CLIPS using overlays
(e.g. using VROOM in Borland C++ 2.0), you should remove the call to
CloseAllBatchSources() in the function CatchCtrlC() in SYSDEP.C.  A failure
to do so will cause rather serious lock-ups when Ctrl-C or Ctrl-Break is
pressed.

3) The function subsetp was designed to work with "true" sets, i.e. those which 
do NOT contain multiple instances of the same atom. If you use "sets" which do 
contain the same atom more than once, then subsetp returns true when the first 
multifield variable argument contains every atom in the second regardless of 
the cardinality of the common atoms, for example

(subsetp (mv-append a b a) (mv-append a b)) returns TRUE 
 
(subsetp (mv-append a b b) (mv-append a b c d)) returns TRUE 

(subsetp (mv-append a b a) (mv-append b a b)) returns TRUE.

If this is not what you want, you will have to check the cardinality yourself.

-------------------------------
MAKEFILES FOR CLIPS version 5.0
-------------------------------
-------------------
-- GENERAL NOTES --
-------------------
Since every make program is different be sure to read the makefile comments
before using them as you will likely have to change the path names defined in
macros to agree with your machine. You may also want to consult the various
vendors reference manuals concerning their versions of make. These make files
above have all been tested and then copied to disk. Before using these make
files make certain the appropriate CLIPS compiler option flags are set on or
off in the file SETUP.H

---------------
----- DOS -----
---------------
If you install the CLIPS source code, makefiles and response files to 
recompile and relink CLIPS for the following DOS C compilers
(we recommend files=20 and buffers=30 in your config.sys) will be included
in the CLIPS SRC subdirectory:

(WARNING!!!  Be sure to use the make program which came with the compiler
including the appropriate version; i.e. don't use Microsoft NMAKE with Turbo C
makefiles or vice versa.):

MSC.MAK and MSC.RSP are the makefile and linker response file for Microsoft C
5.1 (or later) and Microsoft LINK respectively.

TBC.MAK for Borland C++ 2.0 and Turbo C++ 1.0 (as ANSI C NOT C++).
This makefile requires the use of a linker response file, TBC.RSP,
which you will also find on the disk. It needs to be edited to reflect the
actual paths to the system libraries on your machine.

TBCOVL.MAK for Turbo C++ 1.0 (as ANSI C NOT C++) using overlays.
This makefile requires the linker response file named TBCOVL.RSP,
included on the disk. In addition you should use the main program in file
MAINOVL.C NOT the one in file MAIN.C. (TBCOVL.MAK and TBCOVL.RSP automatically
use MAINOVL.C instead of MAIN.C).  The main in MAINOVL.C is designed to
set appropriate stack and buffer sizes and to take advantage 
of expanded or extended memory, if present, for overlay use.

----------------
----- UNIX -----
----------------
Each directory and subdirectory on the UNIX distribution tape has its 
own Imakefile and Makefile files. The Makefile in the clips subdirectory 
is for making the command line executable version of CLIPS, clips. 
The Makefile in the xclips subdirectory is for making the X window System
version of CLIPS, xclips. The Makefile in the color subdirectory is for making 
the color utility. In the top level directory clips5.1 there also is a top
level Imakefile and Makefile that can be used to make all the binaries
(clips, xclips, and color).

If the xmkmf command is available, you can do the following steps 
(press the return key after each command): 

xmkmf
make Makefiles
make depend
make

If the xmkmf command is not available and the imake command (which comes
with the X Window system) is available, you can do the following steps 
(press the return key after each command):

imake -DUseInstalled -I/usr/lib/X11/config 
make Makefiles
make depend 
make

Note that "usr/lib/X11/config" used above may be different in your system.

If both the xmkmf and imake commands are not available, do the following steps 
(press the return key after each command):

make depend
make

NOTES:
-----
The Makefiles are specific for the SUN systems; if another UNIX flatform
is used these Makefiles may have to be modified.

An executable version of color and an executable version of command line
CLIPS also should be in the same directory with "xclips" if you want to run
the color utility or open a command line session of CLIPS while you are in
xclips.

If you have a color monitor, and prefer a color interface, place Xclips in 
your home directory or any other appropriate directories (ask your X guru).
You can modify the color of the interface by running "color" utility.

The X Window interface only comes on the UNIX distribution tape.

Refer to section 7.6 of the Utilities and Interfaces Guide for other details
on building the UNIX executables. 

---------------------
----- Macintosh -----
---------------------
CLIPS and Think C
There are two project files for use with Symantec Think C 4.05 in the Think C 
Project Files folder. The resource file for the Macintosh interface version of 
CLIPS is also in this folder. These project files can also be used with Think 
C 5.0 (just click OK in response to the prompt "This project was created by an 
earlier version of THINK C. Convert it to the current format?"). For specific 
details on creating the Macintosh executables using Think C 4.05 or 5.0, refer 
to section 6.8 of the Utilities and Interfaces Guide.

CLIPS 5.1.        the project file for Think C Macintosh CLIPS
CLIPS 5.1..Rsrc   the resource file for Think C Macintosh CLIPS
CLIPS 5.1G         the project file for Think C generic CLIPS

See Note 14 above on using the optimizer in Think C 5.0.

CLIPS and MPW C
There are two make files for use with MPW C 3.2 in the MPW C Project Files 
folder. The resource file for the Macintosh interface version of CLIPS is also 
in this folder. For specific details on creating the Macintosh executables 
using MPW C 3.2, refer to section 6.8 of the Utilities and Interfaces Guide.

CLIPS 5.1.make     the make file for MPW C Macintosh CLIPS
CLIPS 5.1.r        the resource file for MPW C Macintosh CLIPS
CLIPS 5.1G.make    the make file for MPW C generic CLIPS

We have tested the CLIPS functionality of the executables generated by both MPW
C and Think C. The correct functionality of the Macintosh interface, however, 
has been predominantly tested using the executable generated by Think C.

CRSV and Think C
There is one project file for use with Symantec Think C 4.05 in the CRSV Source
folder. The resource file for the Macintosh interface version of CRSV is also 
in this folder. You MUST use Think C 4.05 to create the CRSV executable. The 
project file CAN NOT be used with Think C 5.0.

CRSV 1.3.         the project file for Think C Macintosh CRSV
CRSV 1.3..Rsrc    the resource file for Think C Macintosh CRSV

The Macintosh window interface only comes on the Macintosh distribution
diskettes.

