;;; -*- Mode:LISP; Package:USER; Base:10; Readtable:Common-Lisp; Patch-File:T -*-
;;; Patch directory for System version 125
;;; Written 22-Jul-88 16:28:20 by pld (Peter L. DeWolf) at site Gigamos Cambridge
;;; while running on Cthulhu from band 3
;;; with System 125.17, ZWEI 125.2, ZMail 73.0, Local-File 75.0, File-Server 24.0, Unix-Interface 13.0, Tape 24.1, Lambda-Diag 17.0, Experimental Kermit 36.5, microcode 1761, SDU Boot Tape 3.14, SDU ROM 8.

(:RELEASED
 ((0 "System Loaded" "pld" NIL)
  (1 "The following special forms didn't have a :source-file-name property:
  DEF, DEFF, DEFUN, DEFSUBST, MACRO, SIGNP" "pld" NIL)
  (2 "The function tv:background-stream is responsible for setting *terminal-io*
to be a tv:background-lisp-interactor.  Change to leave *terminal-io* alone
if it is already a stream.  Thus, PRINTing to this function while in a normal
Lisp Listener will no longer clobber *terminal-io* and PRINTing multiple times
to this function will not generate multiple background-lisp-interactors." "pld" NIL)
  (3 "(disk-save) turns off the Garbage Collector Process before offering to flip
level 2, since having a GC in process when the disk-save enters the microcode
is deadly.  Unfortunately, (gc:reinitialize) doesn't trouble to restart the
GC if it was manually stopped.  Cure: if GC was enabled when we entered
(disk-save), reenable it before entering the microcode." "pld" NIL)
  (4 "Improved logic and error messages for trying to compile a flavor
instance that can't be reconstructed in a load file.  (If the flavor
doesn't handle one of the methods :FASD-FORM or :RECONSTRUCT-INIT-PLIST,
the compiler can't compile an instance.)

Also, provide :FASD-FORM method for SI:HOST flavor.  This means you can
now compile constant references to hosts, e.g.

	 (setq x #FS:UNIX-HOST \"ANGEL\")

This is hardly ever what you really want to do, but at least it works." "keith" NIL)
  (5 "Fix to previous patch to tv:write-user-options; now recognizes strings
(representing hosts) as they are read back in." "saz" NIL)
  (6 "Utilities for SDU-SERIAL-STREAM that, by the way, Kermit now uses.

1. SI:COMBINED-SDU-SERIAL-STREAM-FLAVOR returns the desired flavor based
on combination of flavor options.
2. SI:SDU-SERIAL-STREAM-P is the only way to determine whether something
is a serial stream, due to brain-dead flavor combination which I'm not
going to try to fix right now." "keith" NIL)
  (7 "Fix to si:set-3com-owner and si:set-excelan-owner to not snarf the
respective ethernet boards unless the corresponding driver is loaded.
Doesn't really matter except in the cold load..." "pld" NIL)
  (8 "(= 4\\5 0.8s0) returned NIL because (floatp 0.8s0) returns T,
causing 4\\5 to be coerced to a float for comparison, not a
short-float.  Unfortunately, (= 0.8 0.8s0) returns NIL,
which can't be easily fixed.  We CAN (correctly) coerce
4\\5 to a short-float, however, and solve the initial
problem..." "pld" NIL)
  (9 "Problems with describing an integer type.  If you do:
    (setq a 4)
    (check-type a (integer 5))
you get:
     error: a is not an integer greater than 5
Fixed to be
     error: a is not an integer greater than or equal to 5

If you then do:
    (check-type a (integer (4)))
you get:
     error: a is not an integer greater than 5
Fixed to be
     error: a is not an integer greater than 4

Similar fixes for when the upper bound is specified
inclusively or exclusively." "pld" NIL)
  (10 "lam:dtp-rplacd-forward really needs to have a value." "pld" NIL)
  (11 "QFILE bug: (fs:host-chaos-interrupt-function) failed to match
asynchronous marks with their file handles.  One noticable
example occured when the server got a Disk Full error and the
user was simply left hanging.  Now you are given the debugger
with useful proceed options including: running Dired, calling
(zwei:clean-directory), expunging the directory." "pld" NIL)
  (12 "Fixes to Chaos routing:
  - packets for this host always go through Loopback interface
  - packets for other processors on same bus go through
    Share interface, even if both this processor and
    the other one have Ethernet interfaces.
  - packets for other processors on same bus go
    directly to that processor, not through the
    Ethernet owner! (matters only to 2X2+ or 3X3)" "pld" NIL)
  (13 "more intelligent calculation of line length for finger-arg-prompt" "pld" NIL)
  (14 "The 3com microcode driver had a bug: the packet length returned
by the 3com board had 20 bytes of overhead added in that was not
being subtracted out before setting the int-pkt fill-pointer.
This fails now that set-fill-pointer does bounds checking." "pld" NIL)
  (15 "LOAD-PATCH-FILE used to very strictly enforce the restriction that
\"The use of LOAD in a patch file is not supported.\" This was done by
binding the function LOAD to an error routine.  Unfortunately, this had
a horrible side-effect: if you warm-booted in the middle of this error,
the new \"temporary\" function value of LOAD became permanent.

Now, LOAD itself checks the value of FS:THIS-IS-A-PATCH-FILE and issues
a continuable, not fatal, error.  You can proceed if you dare.  I
believe this is correct; sometimes a patch may need to LOAD something
like a font file." "keith" NIL)
  (16 "When you get a background error with windows locked, the who-line
message now tells the truth about which keys to press to resolve the
problem.  The key for clearing window-system locks is Terminal
Control-Clear-Input, Not M-C-Clear-Input.  (I always wondered why that
didn't work.)" "keith" NIL)
  (17 "Rationalize treatment of various READer end-of-file conditions.

1. Packages not followed by symbols -- reading things like \"foo:\" used
to blow up with a datatype comparison error from (=) . [I type things
like that a lot when I stay up too late.]  Now, signals a CERROR, so in a
listener it just prompts \"EOF after package prefix\".

2. Used to be, all READ-END-OF-FILE errors had the proceed option that said,
\"Close off all unfinished lists.\"  What a crock - that hardly applies to strings
and (now) unterminated symbols.  I defined flavors and separate :NO-ACTION proceed
methods for these other read-end-of-file types.  Now:

a) with an unterminated string, readers offer to return the null string.
That's what you got before.
b) with an unterminated symbol, readers offer to return NIL.  
That's new.
c) with an unterminated list, you get the same behavior as before." "keith" NIL)
  (18 "Cosmetic change to error strings as processed by QFILE-PROCESS-ERROR-NEW:
we now strip off any \".\"'s which appear at the end of qfile error
strings, as some of this function's callers expect to be able to append
text to the end of this returned string in constructing longer error
messages." "saz" NIL)
  (19 "The NETWORK package doesn't really want to import/export the
implementation specific variable ZUNDERFLOW -- better it
should use the macro WITHOUT-FLOATING-UNDERFLOW-TRAPS,
which is implemented in terms of ZUNDERFLOW on the Lambda,
but need not be on other machines..." "pld" NIL)
  ))