Changes to Nisp since the manual:

August, 1992:

It should now be possible to USE the NISP package in some other
package and have reasonable things happen.  However, there are several
Nisp constructs whose names clash with the civilized world's usage.
To compensate, there are synonyms for all these touchy symbols:

   LOOP -- REPEAT
   DEFTYPE -- NISPDEFTYPE,DEFNISPTYPE
   DEFCLASS -- NISPDEFCLASS,DEFNISPCLASS
   COMPLEMENT -- SET-DIFFERENCE 
   SYMBOL -- BUILD-SYMBOL

If you insist on the Nisp versions, the function
(NISP-PENETRATE-PACKAGE p) does the appropriate shadowing-imports to
get all the naughty symbols imported into the package p.
(NISP-WITHDRAW-FROM-PACKAGE p) undoes this.  (USE-NISP) does this for the user
package, and in addition sets the readtable to the NISP-READ-TABLE*.
(UNUSE-NISP) reverses the process.

New flag: NISCOM-RELOAD*: If you say (NISCOM -F ...), presumably you
mean to reload the file after forcing its recompilation.  If this
variable has value ASK (the default), you will be asked whether to
reload; if it's any other non-#F value, the reload will happen
automatically. 


January, 1992:

In (EARROR function val -msgs-), the val can one of the special flags
-NOCONTINUE or -NOVALUE.  The former indicates a fatal error, from
which the user will not be allowed to continue.  The latter indicates
that the value of the EARROR will be ignored, so the user will not be
prompted for a value.

If you put the flag :INFINITE in the body of a LOOP, then no warning
will be issued if Nisp can find no termination test.

(MULTVALS -type-var-list-) is a useful alternative to (MLV -types-).
The vars in the MULTVALS are discarded, and their types used to
generate an MLV, but the vars can be mnemonic, and they can save you
from repeating type names.  For example, if a procedure returns two
lists of integers, you can write
      (MULTVALS ODDS EVENS - (LST integer))
instead of
          (MLV (LST integer) (LST integer))

