Skip to content
Snippets Groups Projects
  1. Dec 19, 1998
  2. Jul 17, 1998
  3. Jul 14, 1998
    • pw's avatar
      This revision merges in many of the fixes for ANSI condition types · 42efe00d
      pw authored
      in various calls to ERROR. Those easily handled by using new condition
      types simple-file-error and simple-program-error are included.
      
      The only functional change here is that the function CHARACTER no longer
      accepts an integer argument so as to be ANSI compliant. This may
      break some code.
      42efe00d
  4. Jun 16, 1998
  5. Mar 21, 1998
  6. Mar 01, 1998
  7. Sep 13, 1997
  8. Sep 03, 1997
  9. Jun 05, 1997
  10. May 08, 1997
  11. Feb 08, 1997
  12. Feb 05, 1997
  13. Jan 18, 1997
  14. Oct 31, 1994
  15. Apr 06, 1994
    • hallgren's avatar
      Added: · be072b7d
      hallgren authored
      (defsetf sap-ref-64 %set-sap-ref-64) and
      (defsetf signed-sap-ref-64 %set-signed-sap-ref-64)
      for the Alpha.
      be072b7d
  16. Feb 11, 1994
  17. Jul 17, 1993
  18. Jul 02, 1993
  19. Jun 24, 1993
  20. May 06, 1993
  21. Mar 01, 1993
  22. Feb 26, 1993
  23. Feb 06, 1993
  24. Feb 04, 1993
  25. Sep 01, 1992
  26. Aug 13, 1992
  27. Apr 04, 1992
  28. Apr 02, 1992
  29. Mar 31, 1992
    • wlott's avatar
      Fixed bug in NTH-VALUE where it expanded into bogus code unless ``n'' was a · 918ab682
      wlott authored
      constant integer.
      918ab682
    • wlott's avatar
      X3J13 cleanup SETF-MULTIPLE-STORE-VARIABLES: · 0a06b2a8
      wlott authored
        Extend the semantics of the macros SETF, PSETF, SHIFTF, ROTATEF, and
        ASSERT to allow "places" whose SETF methods have more than one "store
        variable".  In such cases, the macros accept as many values from the
        newvalue form as there are store variables.  As usual, extra values
        are ignored and missing values default to NIL.
      
        Extend the long form of DEFSETF to allow the specification of more
        than one "store variable", with the obvious semantics.
      
        Clarify that GET-SETF-METHOD signals an error if there would be more
        than one store-variable.
      0a06b2a8
  30. Feb 24, 1992
  31. Feb 21, 1992
  32. Nov 05, 1991
  33. Jul 11, 1991
  34. May 24, 1991
  35. May 08, 1991
    • ram's avatar
      Frobbed SETF a bit more. We still always call GET-SETF-METHOD to let it do its · 2bc53d6a
      ram authored
      thing, but if the result is just a call to the inverse, then directly call the
      inverse w/o any let binding.  This makes setf inverses usable without the full
      interpreter.
      2bc53d6a
    • ram's avatar
      Changed DEFSETF and DEFINE-SETF-METHOD to call a common subfunction, · 1f9b059a
      ram authored
      %DEFINE-SETF-MACRO, which checks for any existing definition as a slot accessor
      or other setf function.
      
      Changed GET-SETF-METHOD to ignore setf macros (always global) when there is a
      local macro or function.
      
      Changed SETF to always call GET-SETF-METHOD, instead of special-casing setf
      inverses.  I was tired to keeping the duplicated code consistent.
      
      Generalized the special casing in SETF of APPLY.  We now go for the SETF
      function when called on any symbol in the Lisp package.  Now SETF of APPLY will
      work on all Common Lisp functions, instead of just two.
      1f9b059a
Loading