Skip to content
Snippets Groups Projects
  1. Apr 02, 2008
  2. Apr 01, 2008
  3. Mar 28, 2008
  4. Mar 26, 2008
  5. Mar 25, 2008
    • agoncharov's avatar
      White space noise for CVS commit testing · 152bc680
      agoncharov authored
      152bc680
    • rtoy's avatar
      Make compiler and interpreter handle slot-value the same. See thread · 4e65ef5d
      rtoy authored
      http://article.gmane.org/gmane.lisp.cmucl.devel/10471.
      
      These changes make the compiler and interpreter behave the same, and,
      as a side-effect, makes Nicolas's code work as he wants.
      
      pcl/slots.lisp:
      o Add LEGAL-SLOT-NAME-P-INTERNAL that returns two values.  If the
        slot-name is legal, return T.  If illegal, return NIL and a string
        indicating why.
      o Use this new function in the compiler macros for SLOT-VALUE, (SETF
        SLOT-VALUE) and SLOT-BOUNDP so that we use the fast ACCESSOR-*
        versions only when we know the slot-name is legal.  Otherwise, the
        compiler macros give up.
      
      pcl/methods.lisp:
      o Change the method LEGAL-SLOT-NAME-P to use
        LEGAL-SLOT-NAME-P-INTERNAL.
      o Update the call to LEGAL-SLOT-NAME-P in SHARED-INITIALIZE since
        LEGAL-SLOT-NAME-P returns 2 values now.
      4e65ef5d
  6. Mar 21, 2008
  7. Mar 19, 2008
  8. Mar 18, 2008
  9. Mar 16, 2008
  10. Mar 15, 2008
    • agoncharov's avatar
      Getting rid of some compiler warnings: · 44e0351e
      agoncharov authored
        * Eliminate `printf' format string and the following arguments
          conflicts.
      
        * A variable may be used uninitialized.
      
        * A variable may be defined but not used.
      44e0351e
  11. Mar 13, 2008
    • rtoy's avatar
      Fix off-by-one bug in ~R which prevents printing numbers from 10^63 to · 971d3122
      rtoy authored
      10^66-1.  10^63 is a vigintillion.  (From SBCL).
      971d3122
    • rtoy's avatar
      (format nil "~5f" 1d-10) was printing out way too many zeroes, · a660c8de
      rtoy authored
      exceeding the specified width.  I think the correct answer is
      ".0000".
      
      So, add a parameter, allow-overflow-p, to FLONUM-TO-STRING to allow
      the width constraint to be exceeded.  This defaults to T.
      FLONUM-TO-STRING looks at this and decides whether or not to print out
      all the leading zeroes or not.  In FIXED-FORMAT-AUX, set
      allow-overflow-p to NIL so we don't exceed the width.
      
      I wish there were another way to do this, but I can't think of one
      right now.
      
      All print tests pass, and add the following test:
      
      (format nil "~5F" 1d-10) -> ".0000"
      
      print.lisp:
      o Change FLONUM-TO-STRING to use keyword parameters instead of
        optional parameters.
      o Add :ALLOW-OVERFLOW-P, defaulting to T.
      o Use :ALLOW-OVERFLOW-P to determine if all the leading zeroes should
        be printed or not.
      
      format.lisp:
      o Update calls to FLONUM-TO-STRING to use keywords parameters.
      o In FIXED-FORMAT-AUX, set :ALLOW-OVERFLOW-P to NIL
      a660c8de
  12. Mar 05, 2008
  13. Mar 03, 2008
  14. Feb 29, 2008
  15. Feb 28, 2008
  16. Feb 27, 2008
    • cshapiro's avatar
      1187403e
    • rtoy's avatar
      Merge fix from release-19e-branch. os_validate should return NULL on · 972fe2bf
      rtoy authored
      failure instead of -1.
      972fe2bf
    • rtoy's avatar
      c4061b8f
    • rtoy's avatar
      Trac ticket #13. · 74f5a075
      rtoy authored
      Basically caused by a change of exponent due rounding of the number
      for printing.  0.999999 might get printed as 1.000.  The original
      number had an exponent of -1, but the printed number has an exponent
      of 0, and we need to account for this.
      
      code/print.lisp:
      o Modify FLONUM-TO-STRING to take into account of the actual and
        printed exponent of the number.  Return an extra value to indicate
        if rounding has the exponent to change.
      
      code/format.lisp:
      o Use the new return value from FLONUM-TO-STRING to tell us if we need
        to adjust the printed exponent to account for the rounding change.
      
      All print tests still pass, and we add the following tests:
      
      (assert (string= (format nil "~11,3,2,0,'*,,'EE" .99) "  0.990E+00"))
      (assert (string= (format nil "~11,3,2,0,'*,,'EE" .999) "  0.999E+00"))
      (assert (string= (format nil "~11,3,2,0,'*,,'EE" .9999) "  0.100E+01"))
      (assert (string= (format nil "~11,3,2,0,'*,,'EE" .0000999) "  0.999E-04"))
      (assert (string= (format nil "~11,3,2,0,'*,,'EE" .00009999) "  0.100E-03"))
      (assert (string= (format nil "~11,3,2,,'*,,'EE" .00009999) "  9.999E-05"))
      (assert (string= (format nil "~11,3,2,,'*,,'EE" .000099999) "  1.000E-04"))
      74f5a075
  17. Feb 14, 2008
  18. Feb 13, 2008
  19. Feb 09, 2008
  20. Feb 08, 2008
    • rtoy's avatar
      o Don't wrap the body in an #ifndef/#endif because this file is · 8be3ebd1
      rtoy authored
        intentionally included multiple times in undefineds.c and is
        expected to do something each time.
      o Add mprotect
      o Add a few more functions for sparc that were missing.  (Only matters
        for non-linkage-table builds.  Shouldn't have any affect on
        linkage-table builds.)
      8be3ebd1
Loading