1. 15 Nov, 2016 5 commits
  2. 14 Nov, 2016 1 commit
  3. 06 Nov, 2016 1 commit
  4. 26 Oct, 2016 1 commit
  5. 12 Oct, 2016 3 commits
  6. 09 Oct, 2016 1 commit
  7. 08 Oct, 2016 7 commits
  8. 25 Sep, 2016 2 commits
    • Robert Goldman's avatar
      Fix build on CCL/Windows. · 46eb49bf
      Robert Goldman authored
      The code for %POSIX-SEND-SIGNAL -- which isn't invoked on Windows
      anyway, was crashing on Windows build -- because of differences in
      function signatures on CCL Windows/other.  Fixed this by simply making
      %POSIX-SEND-SIGNAL a stub on Windows.  I couldn't remove it altogether,
      because deciding whether to invoke it is a decision made at run-time,
      not compile-time.
    • Elias Pipping's avatar
      Export process-info-pid · 8f9db9ed
      Elias Pipping authored
  9. 24 Sep, 2016 14 commits
  10. 09 Sep, 2016 2 commits
  11. 02 Sep, 2016 3 commits
    • Elias Pipping's avatar
      Clasp does not support asynchronous processes. · af272448
      Elias Pipping authored
      The functions that can allegedly be called on clasp in analogy to ecl
      do not exist.  Calling %run-program would yield a cryptic error prior
      to this change because `apply` is called with a list of arguments but
      no function.
    • Elias Pipping's avatar
      Change :if-*-exists default to :supersede · c01c86f5
      Elias Pipping authored
      The difference between :overwrite (the former default) and :supersede
      is only that the latter should not lead to an error if the file does
      not exist. There is plenty of support for :supersede behaviour (not
      necessarily under that name) but not for :overwrite behaviour. Hence
      we make it the default and add a normaliser.
      Since normalisation is currently only necessary for CLISP and CLISP
      only has :if-output-exists support (not :if-error-output-exists or
      :if-input-does-not-exist), we only translate :if-output-exists for now.
    • Elias Pipping's avatar
      Bug fix: Have %wait-process-result fail on CLISP · 9198e77f
      Elias Pipping authored
      On platforms where %wait-process-result is not supported,
      an error is supposed to be raised. Since the error is only
      raised when the process-info field 'process' is non-nil, on
      CLISP (where 'process' is always NIL), the function instead
      behaves like a dummy.