*patches*

The value of this variable is alist witch the keys being keywords that describe the patch category and the values being lists describing the individual patches loaded into the image. For a patch file to be noticed, it must contain a defpatch form. All official Allegro CL patches contain such a form.

The values in the alist are (as said above) themselves lists, with four elements:

1. A string providing the name of the patch that an attempt was made to load.
2. The version of the patch (an integer).
3. A string providing a short description of the patch.
4. nil if the patch was loaded sucessfully or a string explaining why it was not loaded.

Here is an example of several entries (you may not see these exact patches), first some :compiler patches and then a few :lisp patches:

((:compiler
  ("fb006" 1 "Allow deprecation of time consuming compiler switches." nil)
  ("fb005" 1 "Fix an immediate-args float return value bug in x86-64." nil)
  ("fb004" 1 "Fix immed-args register allocation for x86-64." nil)
  ("fb002" 1
   "Fixes formatting failures in the (:explain :tailmerging) declaration."
   nil)
  ("fb001" 1 "Fix same-register-multiply problem." nil))
 (:lisp
  ("fa026" 1 "Fix single-value-return versions of floor and ceiling." nil)
  ("fa025" 2 "Macros and support objects for using SMP macros in acl 8.1."
   nil)
  ...)

Note particularly the last value of the four in the individual patch lists: nil if the patch was loaded sucessfully. All these patches were loaded. If the load was unsuccessful, there would be a string explaining why it was not loaded. If the last value is not nil, the patch was not loaded and whatever it is designed to fix/change is unfixed/unchanged.

Copyright (c) 1998-2019, Franz Inc. Oakland, CA., USA. All rights reserved.
This page was not revised from the 9.0 page.
Created 2015.5.21.