1. 18 Aug, 2017 2 commits
  2. 02 Aug, 2017 1 commit
  3. 04 Jul, 2017 1 commit
  4. 15 Jun, 2017 1 commit
  5. 11 Jun, 2017 2 commits
  6. 09 Jun, 2017 1 commit
  7. 08 Jun, 2017 3 commits
  8. 07 Jun, 2017 2 commits
  9. 04 Jun, 2017 1 commit
  10. 03 Jun, 2017 5 commits
  11. 01 Jun, 2017 10 commits
  12. 23 May, 2017 1 commit
  13. 15 May, 2017 3 commits
  14. 27 Apr, 2017 1 commit
    • Fix signalling simple error with #\~ in format string · 6a866834
      (Alan Ruttenberg)
      
      Signaling an simple error would signal another error if the message
      happened to have a ~ in it, since in simple cases there are no format
      args, but format is called with the message string.
      
      We fix this by changing all cases in the source where there were calls
      to setFormatControl(x) are followed by setFormatArguments(NIL). In
      such cases we changed setFormatControl(x) ->
      setFormatControl(x.replaceAll("~","~~")), which is the CL:FORMAT
      recipe for escaping a #\~ character.
      
      To replicate this error, place the following in a file
      <file:~/work/abcl/double-error.lisp>.
      
          (defun foo (x) (funcall x))
      
      then
      
          CL-USER> (compile-file "~/work/abcl/double-error")
          ; Compiling /Users/evenson/work/abcl/double-error.lisp ...
          ; (DEFUN FOO ...)
          ; Wrote /Users/evenson/work/abcl/double-error.abcl (0.015 seconds)
          #P"/Users/evenson/work/abcl/double-error.abcl"
          NIL
          NIL
          CL-USER> (foo '~)
      
      gives
      
          Error (FORMAT-ERROR) during printing: #<PROGRAM-ERROR {264F63C5}>
             [Condition of type PROGRAM-ERROR]
      
      Merges <https://github.com/armedbear/abcl/pull/41>.
  15. 17 Apr, 2017 2 commits
  16. 16 Apr, 2017 1 commit
  17. 07 Apr, 2017 1 commit
  18. 30 Mar, 2017 1 commit
  19. 28 Mar, 2017 1 commit