1. 09 May, 2014 1 commit
  2. 28 Mar, 2014 1 commit
  3. 25 Mar, 2014 2 commits
  4. 24 Mar, 2014 2 commits
  5. 22 Mar, 2014 1 commit
  6. 21 Mar, 2014 1 commit
  7. 17 Mar, 2014 4 commits
  8. 16 Mar, 2014 1 commit
  9. 07 Mar, 2014 1 commit
    • Francois-Rene Rideau's avatar
      plan changes: · b570ee9f
      Francois-Rene Rideau authored
      * move *all* timestamp management to COMPUTE-ACTION-STAMP.
      * goodbye visit-dependencies, move its functionality to map-direct-dependencies,
      * refactored map-direct-dependencies and co to always take a plan object.
      * modified clients of map-direct-dependencies and co to pass a proper plan, or t.
      Add invalid file with false if-feature to bundle.
      b570ee9f
  10. 06 Mar, 2014 2 commits
  11. 05 Mar, 2014 1 commit
  12. 04 Mar, 2014 1 commit
  13. 01 Mar, 2014 1 commit
    • Francois-Rene Rideau's avatar
      Fixes and refactoring of asdf/bundle and uiop/image for ECL. · c52a4f83
      Francois-Rene Rideau authored
      Testing the latest cl-launch with ECL showed massive bitrot in the bundle support for ECL.
      * Make better use of ASDF3's class hierarchy in redefining asdf/bundle,
        by removing and adding the mixins: goodbye bundle-compile-op and monolithic-,
        hello link-op and gather-op. Also, reinstate bundle-system as a class
        to hold prologue and epilogue (but do we need these, now with portable ASDF3 image support?)
      * rename binary-op to deliver-asd-op, same for monolithic-
      * Introduce image-op as a superclass of program-op,
        for dumping an executable image with the regular top-level.
      * Redo the way operation flags are or aren't propagated:
        gather-op explicitly does not pass the flags,
        so toplevel options are for the toplevel build only
        -- though they belong to the system, not the operation.
        Therefore get rid of no-ld-flags-op -- if there are flags to pass,
        they should be passed explicitly in gather-op;
        or more likely, they might be slots in the system, or the plan,
        or special variables for the current session.
        OPERATE tries harder to preserve the original-initargs,
        which are not clobbered by asdf/bundle's initialize-instance anymore.
      * Punt for command-line-arguments on LispWorks,
        so the user has a slight chance of setting them.
      c52a4f83
  14. 28 Feb, 2014 1 commit
  15. 21 Feb, 2014 1 commit
  16. 18 Feb, 2014 1 commit
  17. 12 Feb, 2014 1 commit
  18. 27 Jan, 2014 2 commits
    • Francois-Rene Rideau's avatar
      More cleanups: · c7d1ce63
      Francois-Rene Rideau authored
      * Add some comments on TRAVERSE-ACTION; expand those on SOURCE-FILE-TYPE.
      * Remove a few unnecessary input-files or output-files methods
      * Remove (declare (ignorable ...)) for specialized arguments. Specialize a few arguments to T.
      * Remove most when-upgrading methods, since we drop data on old incompatible ASDFs.
      c7d1ce63
    • Francois-Rene Rideau's avatar
      Cleanups done or initiated during the ASDF Walkthrough. · f71a8b99
      Francois-Rene Rideau authored
      * load-op needn't be sideway, its sideway dependencies are already provided by prepare-op
      * compile-op should use compile-op (default) not load-op as its downward-operation.
      * no need for an input-files method for prepare-op, nil is the global default.
      * Some documentation for compute-action-stamp.
      * Don't skip upgrade from 1.x on Allegro anymore, since we now correctly punt.
      * Instead of asdf/package:define-package, use the canonical name uiop/package:define-package
      f71a8b99
  19. 26 Jan, 2014 1 commit
  20. 22 Jan, 2014 1 commit
  21. 21 Jan, 2014 3 commits
    • Robert P. Goldman's avatar
      5e21bb43
    • Robert P. Goldman's avatar
      Raise a continuable error when instantiating an unpatched OPERATION. · 8fa22cd5
      Robert P. Goldman authored
      The behavior of OPERATION has changed: previously it would act roughly like
      LOAD-OP, and automatically have dependencies, but now that behavior has been
      removed in a clean-up. In order to support programmers, we attempt to detect
      programmer-defined OPERATION subclasses and signal an error if we believe they
      are unpatched.
      
      The new dependency-handling is implemented in the classes DOWNWARD-OPERATION,
      UPWARD-OPERATION, SIDEWAY-OPERATION, SELFWARD-OPERATION, and the newly-added
      NON-PROPAGATING-OPERATION.
      
      To detect unpatched OPERATION classes, when we are instantiating an OPERATION,
      we check to make sure it has one of the above classes as a superclass.  If it
      does not, we raise a continuable error.  This is done in an INITIALIZE-INSTANCE
      :BEFORE method on OPERATION. We considered trying to detect the definition of
      OPERATION subclasses, but because the MOP is not standard, that approach was
      rejected as infeasible.
      
      Add NON-PROPAGATING-OPERATION as superclass where needed.
      
      Further checks and some documentation.
      
      Thanks to Fare for advice.
      
      Check that no OPERATION is both propagating and non-propagating.
      
      Thanks to Fare for the suggestion.
      8fa22cd5
    • Robert P. Goldman's avatar
      Refined the earlier warning about BUNDLE-OP. · 989670e5
      Robert P. Goldman authored
      It turns out it's only the BASIC-FASL-OP, not all the BUNDLE-OPs, that's
      broken on Mac OSX with ABCL and ECL.  Refined the check.
      989670e5
  22. 20 Jan, 2014 1 commit
  23. 08 Jan, 2014 2 commits
  24. 20 Nov, 2013 1 commit
  25. 09 Oct, 2013 1 commit
  26. 10 Sep, 2013 1 commit
  27. 26 Jun, 2013 1 commit
  28. 13 May, 2013 1 commit
  29. 04 Apr, 2013 1 commit
  30. 03 Apr, 2013 1 commit