1. 25 Nov, 2016 2 commits
    • Robert Goldman's avatar
      Disable RUN-SHELL-COMMAND on ECL + Windows. · 8aec89e0
      Robert Goldman authored
      RUN-SHELL-COMMAND requires string commands to RUN-PROGRAM to function,
      and these are not supported on the Windows version of ECL.  Signal
      NOT-SUPPORTED-ERROR.
      8aec89e0
    • Robert Goldman's avatar
      Clarify PARAMETER-ERROR. · d619b96f
      Robert Goldman authored
      Previous error string implied that UIOP *never* supported string
      commands on Windows, but actually we do support them on some lisp
      implementations.
      d619b96f
  2. 23 Nov, 2016 2 commits
    • Francois-Rene Rideau's avatar
      Adjust RUN-PROGRAM with a string COMMAND on Windows · b1c3fbb4
      Francois-Rene Rideau authored
      Always go through CMD in that case, including on Allegro and CLISP, since
      the previous behavior is simultaneously non-portable, error-prone and limited;
      better to provide a portable well-defined abstraction.
      Users who want more can use the (bad) implementation-specific interfaces,
      or IOlib.
      
      Simplify the call to RUN-PROGRAM.
      Add a PARAMETER-ERROR to %NORMALIZE-COMMAND on unsupported platforms.
      b1c3fbb4
    • Elias Pipping's avatar
      Fix test-run-program on windows · 3c514bfe
      Elias Pipping authored
      We cannot use `exit` on Windows with :force-shell nil (it's a builtin);
      use `cmd /c exit` instead.
      
      Using `exit` on Unix with :force-shell nil may or may not work (it's a
      builtin but CL implementations typically invoke a shell anyway).
      `true` and `false` are guaranteed to exist by the POSIX standard.
      3c514bfe
  3. 22 Nov, 2016 13 commits
  4. 20 Nov, 2016 3 commits
  5. 19 Nov, 2016 1 commit
  6. 15 Nov, 2016 19 commits