Skip to content
Snippets Groups Projects
  1. Dec 04, 2001
  2. Jun 13, 2001
  3. Jun 03, 2001
    • pw's avatar
      From Tim Moore: · a0c0de03
      pw authored
      Arrange for ANSI behaviour regarding DEFMACRO processing. It has
      compile-time effect only at top level now.
      a0c0de03
  4. Mar 13, 2001
  5. Mar 03, 2001
  6. Oct 06, 2000
  7. Aug 10, 2000
  8. Jul 06, 2000
    • dtc's avatar
      Reworking of the values-type system to overcome a number of inconsistencies · daf333f4
      dtc authored
      causing problems:
      
      o Redefine coerce-to-values to convert a single value type into (values type),
        rather than the former definition (values type &rest t). A single value
        type such as fixnum is now equivalent to (values fixnum). Values-type-union
        and values-type-intersection will canonicalise values types with a
        single value such as (values fixnum) back to a single value type
        such as fixnum.
      
      o Now when the compiler makes assertions for the first value of
        continuations that may be generating multiple values it asserts the
        type as (values type &rest t), or as (value &optional type &rest t) if
        it is not sure that the continuation does generate a value.
      
      o Enhance the type check generation to better handle the now common
        values types with optional and rest arguments. Add the new function
        Values-types-asserted which converts asserted optional and rest
        arguments to required arguments that have been proven to be delivered,
        Thus an assertion such as (values &optional fixnum &rest t) will
        generate a fixnum type check if the proven type if (values t).
      
      o The compiler is now far more likely to pickup attempts to use an
        assertion to select a subset of values. For example
        (the (values fixnum) (values x y)) will generated a compiler warning.
      
      o Update single values type assertions where appropriate to clarify that
        the received values may be optional or that multiple values may be
        received. For example, a macro argument which had been asserted to be
        a list via (the list ,...) would now be asserted to be
        (the (values &optional list &rest t)) etc.
      
      o Have the IR1 translator for THE convert single value types into
        (values &optional type &rest t) so that code such as
        (the fixnum (values x y)) will still work acceptably. This does not
        restrict the possible type assertions as the values types may be used
        and are not modified.
      daf333f4
  9. Apr 14, 2000
  10. Sep 15, 1999
  11. Dec 19, 1998
  12. Jul 17, 1998
  13. 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
  14. Jun 16, 1998
  15. Mar 21, 1998
  16. Mar 01, 1998
  17. Sep 13, 1997
  18. Sep 03, 1997
  19. Jun 05, 1997
  20. May 08, 1997
  21. Feb 08, 1997
  22. Feb 05, 1997
  23. Jan 18, 1997
  24. Oct 31, 1994
  25. 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
  26. Feb 11, 1994
  27. Jul 17, 1993
  28. Jul 02, 1993
  29. Jun 24, 1993
  30. May 06, 1993
  31. Mar 01, 1993
  32. Feb 26, 1993
  33. Feb 06, 1993
  34. Feb 04, 1993
  35. Sep 01, 1992
  36. Aug 13, 1992
Loading