1. 17 Mar, 2014 1 commit
  2. 28 Feb, 2014 4 commits
  3. 26 Feb, 2014 1 commit
  4. 25 Feb, 2014 1 commit
  5. 22 Feb, 2014 1 commit
  6. 27 Jan, 2014 2 commits
  7. 08 Jan, 2014 1 commit
  8. 01 Jan, 2014 1 commit
  9. 20 Dec, 2013 1 commit
  10. 19 Dec, 2013 1 commit
  11. 20 Nov, 2013 1 commit
  12. 15 Nov, 2013 1 commit
    • Francois-Rene Rideau's avatar
      UIOP improvements. · cbc92b1b
      Francois-Rene Rideau authored
      Define the :DBG macro, so it's ubiquitously available for print-debugging.
      Define and export nest, so it's always there to prevent indentation drift.
      Tweak restore-image again for better handling of *lisp-interaction*.
      Update docstrings for define-package.
      Define %process-info-pid.
  13. 12 Nov, 2013 1 commit
  14. 05 Nov, 2013 1 commit
  15. 24 Oct, 2013 1 commit
  16. 23 Oct, 2013 2 commits
    • Francois-Rene Rideau's avatar
      package-system: support for quick-build style defpackage-based dependencies. · c609093c
      Francois-Rene Rideau authored
      This is quick-build compatible and fixes lp#1230368.
      To use package-system, just have foo.asd containing
      	(defsystem foo :class package-system)
      at the top of your quick-build hierarchy $FOODIR
      for packages whose name start with "FOO/"
      and ASDF will thereafter look for system "foo/bar/baz" in $FOODIR/bar/baz.lisp.
      Such a file will implicitly have its own system defined;
      its dependencies are computed by scanning the file,
      extracting its first defpackage form,
      and using the packages it uses or imports from
      as a as a specification of what systems it depends on.
      You can register packages as belonging to a system with
      	(asdf:register-system-packages my-system '(package1 package2))
      Using or importing from a package registered to a given system
      will generate a dependency to the registered system.
      Using or importing from a packages registered to the constant symbol T
      will not generate any dependency.
      Using or importing from a packages that is not registered will generate
      a dependency on a system the name of which is the package name downcased.
      All packages that exist at the time ASDF is initially loaded
      are registered to constant symbol T.
      Also, for convenience, introduce :use-reexport and :mix-reexport in
      uiop/package.lisp (of course, no one can rely on it until it's mainstream,
      but better late than never).
      To use this style in a way compatible with older versions of ASDF 3,
      you may use the asdf-package-system extension.
      See lisp-interface-library for a system that uses this style this way.
      Push :asdf-package-system to *features*
    • Francois-Rene Rideau's avatar
      Try to avoid extraneous spaces in redirected command lines · ba8308da
      Francois-Rene Rideau authored
      for the sake of Windows' CMD.EXE.
  17. 21 Oct, 2013 1 commit
  18. 15 Oct, 2013 1 commit
  19. 12 Oct, 2013 2 commits
  20. 11 Oct, 2013 1 commit
  21. 09 Oct, 2013 1 commit
  22. 02 Oct, 2013 1 commit
  23. 30 Sep, 2013 1 commit
  24. 28 Sep, 2013 2 commits
    • Francois-Rene Rideau's avatar
      Various run-program related fixes: · 3176b414
      Francois-Rene Rideau authored
      * have run-program on ECL on SLIME.
      * remove now unnecessary &allow-other-keys from slurp-input-stream and vomit-output-stream.
      * add stripln and :stripped t support to slurp-input-stream string.
      * add convenience functions println and writeln.
    • Francois-Rene Rideau's avatar
      Another reimplementation of run-program. New: · 4caf0cc7
      Francois-Rene Rideau authored
      * it handles INPUT and ERROR-OUTPUT, not just OUTPUT.
      * it accepts PATHNAMEs as I/O designators
      * it works on ECL under SLIME (fixes lp#1232225)
        At the suggestion of stassats, we're always returning an exit code,
        and in a predictable return value position.
        However, both for backward compatibility and usability,
        the OUTPUT slurping results remain the primary return value,
        followed by the ERROR-OUTPUT slurping results, followed by the exit code.
        So far, no one was using multiple values in SLURP-INPUT-STREAM methods,
        so no one will regret that, except people who might have somehow expected
        the old weird behavior of a return code when OUTPUT is NIL or :INTERACTIVE.
      * As another API tweak and improvement, keyword options are now specified
        separately for each of your I/O designators, by putting them your designator
        in a list. A list also distinguishes a string as input from a namestring
        to designate a pathname, i.e. :input '("bar") is the string literal,
        whereas :input "bar" is the file named bar.
      Several fixes and extensions to stream support.
      Only tested so far on Linux x64 with
      ccl clisp sbcl ecl ecl_bytecodes cmucl abcl allegro allegromodern xcl
  25. 16 Sep, 2013 1 commit
  26. 08 Sep, 2013 2 commits
  27. 06 Sep, 2013 1 commit
  28. 07 Aug, 2013 1 commit
  29. 26 Jun, 2013 1 commit
  30. 22 May, 2013 1 commit
  31. 21 May, 2013 1 commit
    • Robert P. Goldman's avatar
      Fixes for UIOP:RUN-PROGRAM on ACL. · 6510db1e
      Robert P. Goldman authored
      On ACL, the :INPUT and :OUTPUT arguments to EXCL:RUN-SHELL-COMMAND take
      NIL for the behavior of inheriting input and output handles from the
      Lisp process.  These were encoded as T in UIOP:RUN-PROGRAM, instead of
      NIL, causing ACL to get errors trying to open T as a file designator.
      Added a couple of test cases to test-run-program.script to illustrate
      the problem.
      Note that this fix does not provide the prescribed behavior for :OUTPUT
      NIL (which should take the program's output and throw it on the floor).
      There is a TODO in uiop:run-program explaining what's missing.  In
      brief, ACL's EXCL:RUN-SHELL-COMMAND does not support this behavior out
      of the box, so one would have to capture the program's output, and then
      throw it on the floor.
  32. 16 May, 2013 1 commit