1. 06 Oct, 2016 1 commit
    • Elias Pipping's avatar
      Clean up use of *features* · 7e361dc2
      Elias Pipping authored
      In particular:
       - clasp does not define :ecl
       - use :os-unix instead of :unix
       - use :os-windows instead of :mswindows or :windows
       - use :os-macosx instead of :darwin
       - use :lispworks7+ instead of :lispworks7
      7e361dc2
  2. 21 Nov, 2014 1 commit
  3. 07 Oct, 2014 1 commit
  4. 17 Mar, 2014 3 commits
  5. 08 Oct, 2013 1 commit
  6. 25 Jan, 2013 1 commit
    • Francois-Rene Rideau's avatar
      2.26.146: restore W-C-U around perform-plan for backward compatibility. · db1cebf7
      Francois-Rene Rideau authored
      Also, move entry-point into system and remove class bundle-system.
      I was tempted to have test-op call it, but then it's a problem
      when the base system has a non-test entry-point, so we probably need
      a separate test-entry-point slot.
      
      Update the default *asdf-debug-utility* to do more of the right thing.
      
      Update changelog.
      
      Tweak package to avoid triggering a bug in ABCL trunk.
      db1cebf7
  7. 21 Jan, 2013 2 commits
  8. 18 Jan, 2013 1 commit
  9. 16 Jan, 2013 1 commit
    • Francois-Rene Rideau's avatar
      2.26.100: checkpointing a lot of progress. · aa5cba5d
      Francois-Rene Rideau authored
      * Pathname support has been cleaned up, yet again,
       extending and renaming COERCE-PATHNAME into PARSE-UNIX-NAMESTRING,
       also ENSURE-PATHNAME, many docstrings, and plenty of small enhancements.
      * Bundles were refactored to take advantage of the new, more sensible,
       component-depends-on semantics.
      * Image support was cleaned up again, and program-op was implemented
       to produce a standalone executable on supported platforms;
       a working hello-world-example is included amongst tests.
      * The *compile-file-function* indirection was removed, with the
       ECL and MKCL object file support
       being folded into compile-file* instead.
      * systems now can have NIL as component-pathname,
       instead of providing a non-sensible bogus pathname
       when no sensible pathname was determined.
       Most of our pathname functions have sensible default behavior
       when provided NIL instead of a pathname as an argument.
      aa5cba5d