Skip to content
Snippets Groups Projects
  1. Aug 01, 2005
    • rtoy's avatar
      o CLHS 22.3.3.2 (~E) says prin1 omits the plus sign of the exponent if · b70016bc
      rtoy authored
        it is non-negative.  Adjust PRINT-FLOAT-EXPONENT accordingly.
      o OUTPUT-FLOAT-AUX prints out 1d23 as "1.0d23".  This differs from how
        FORMAT ~E prints out that number.  Adjust OUTPUT-FLOAT-AUX to match
        what ~E does.  (Are there other cases that we're missing?)
      b70016bc
  2. Jul 13, 2005
  3. Jul 12, 2005
  4. Jul 07, 2005
  5. Jul 05, 2005
  6. Jul 01, 2005
  7. Jun 30, 2005
  8. Jun 23, 2005
  9. Jun 20, 2005
  10. Jun 19, 2005
  11. Jun 15, 2005
  12. Jun 14, 2005
    • rtoy's avatar
      Some fixes for floating-point printing bugs reported by Bruno Haible, · 1031c478
      rtoy authored
      cmucl-imp, on or around 2005/06/13.
      
      Some useful tests:
      
      (format nil "~9,3,2,0,'%G" 0.0314159)
      Expected: "0.314e-01"
      
      
      (format nil "~9,3,2,-2,'%@e" 3.14159)
      Expected: "+.003E+03"
      
      
      (format nil "~6,2,1,'*F" 3.14159)
      Expected: " 31.42"
      
      (format nil "~9,0,6f" 3.14159)
      Expected: " 3141590."
      
      (let (x)
       (dotimes (k 13 x)
        (setq x (cons (format nil "~%Scale factor ~2D: |~13,6,2,VE|"
                (- k 5) (- k 5) 3.14159) x))))
      
      ("
      Scale factor  7: | 3141590.e-06|"
       "
      Scale factor  6: | 314159.0e-05|"
       "
      Scale factor  5: | 31415.90e-04|"
       "
      Scale factor  4: | 3141.590e-03|"
       "
      Scale factor  3: | 314.1590e-02|"
       "
      Scale factor  2: | 31.41590e-01|"
       "
      Scale factor  1: | 3.141590e+00|"
       "
      Scale factor  0: | 0.314159e+01|"
       "
      Scale factor -1: | 0.031416e+02|"
       "
      Scale factor -2: | 0.003142e+03|"
       "
      Scale factor -3: | 0.000314e+04|"
       "
      Scale factor -4: | 0.000031e+05|"
       "
      Scale factor -5: | 0.000003e+06|")
      
      
      code/format.lisp:
      o If the scale factor (k) is negative, the min number of digits to
        print is 1, not (- 1 k) because that prints too many if the field is
        too short.  Setting fmin to fdig is ok if k >= 0.  (See scale factor
        test above.)
      o If flonum-to-string returns with a trailing decimal point, we don't
        need to decrement spaceleft because that deletes a white-space
        character.  (See first scale factor 7 test above.)
      
      code/print.lisp:
      o We need to adjust the number of digits to be printed to include the
        scale factor.  See tests above.
      1031c478
  13. Jun 13, 2005
    • rtoy's avatar
      Save xref information to fasls. · 624c3dc2
      rtoy authored
      This is done by faking it.  The file being compiled is compiled as
      usual, but we append fake forms to the file as if they came from the
      file.  These fake forms insert the necessary information into the xref
      databases when the fasl is loaded.
      
      To support this feature, we also updated COMPILE-FILE to recognize the
      :xref keyword arg.  Set this to non-NIL to enable computing and saving
      xref information.
      
      code/exports.lisp:
      o Update XREF exports
      
      compiler/fndb.lisp:
      o Update with new definition of COMPILE-FILE.
      
      compiler/main.lisp:
      o Append fake forms to the file being compiled to save xref
        information to the fasl.  This clears out any xref info we might
        have for the file, and inserts the necessary xref information into
        the database.
      o Add :XREF keyword arg to COMPILE-FILE.  Default value of :XREF is
        C::*RECORD-XREF-INFO*.
      
      compiler/xref.lisp:
      o Add function to invalidate xref info for a given namestring, so we
        can reset the info when a fasl with xref info is loaded.
      o Add a function to find all xref information for a given pathname.
        Used for saving xref info to a fasl.
      624c3dc2
  14. Jun 01, 2005
  15. May 26, 2005
  16. May 23, 2005
  17. May 19, 2005
  18. May 17, 2005
  19. May 12, 2005
  20. May 11, 2005
    • rtoy's avatar
      Supply a pathname for simple-file-error in make-pathname when we have · 73409eb1
      rtoy authored
      :absolute or :wild-inferiors followed by :up or :back.
      
      Not exactly sure what pathname to use here since we don't accept these
      pathnames.  So we use the given pathname with the :up/:back deleted.
      And the format strings gives more info about what happened.
      
      Fixes ansi-test MAKE-PATHNAME-ERROR-RELATIVE-WILD-INFERIORS-UP and
      friends.
      73409eb1
    • rtoy's avatar
      o Make VALID-FUNCTION-NAME-P the function name, even if it's not a · c213d403
      rtoy authored
        valid function name.
      o Make the setf function-name-syntax try return the function name even
        if it's not a valid setf function name.
      o Use the above changes to fill out more completely and correctly the
        simple-type-error in FDEFINITION-OBJECT, when the function name is
        not valid.
      
      This fixes ansi-tests for fboundp and friends where the datum was a
      type of expected-type or where the datum had the wrong name.
      c213d403
  21. May 10, 2005
  22. May 09, 2005
  23. May 06, 2005
  24. May 03, 2005
  25. Apr 30, 2005
  26. Apr 28, 2005
  27. Apr 24, 2005
  28. Apr 22, 2005
Loading