1. 17 Jan, 2022 2 commits
  2. 10 Jan, 2022 3 commits
  3. 07 Jan, 2022 2 commits
  4. 06 Jan, 2022 2 commits
  5. 05 Jan, 2022 10 commits
    • Robert Goldman's avatar
      Bump version to 3.3.5.5 · 864bbe24
      Robert Goldman authored
      864bbe24
    • Robert Goldman's avatar
      Merge branch 'iss94' into 'master' · a3059e88
      Robert Goldman authored
      Ensure version slot of preloaded systems is correct after an upgrade
      
      Closes #94
      
      See merge request !194
      a3059e88
    • Eric Timmons's avatar
      Fix test-module-excessive-depend.script · eebb10b6
      Eric Timmons authored
      This test has probably been broken for a very long time, but it was missed due
      to UPGRADE-ASDF returning T all the time. This meant that the first LOAD-OP was
      performed in a new session, *not* the session created at the top of the
      file. Once UPGRADE-ASDF was fixed, then the done status of the LOAD-OP was
      persisted, resulting in the next LOAD-OP being a no op.
      
      However, this breakage wasn't immediately apparent because FILE-WRITE-DATE was
      compared with #'>= and the PLAN was not asserted to actually contain the
      operations we wanted to see. So on a fast computer (unless you got really
      unlucky) you'd never see the failed test.
      eebb10b6
    • Eric Timmons's avatar
      Disable upgrade tests on Clasp · 89f13f22
      Eric Timmons authored and Robert Goldman's avatar Robert Goldman committed
      89f13f22
    • Eric Timmons's avatar
      Use REGISTERED-SYSTEM to find preloaded system instead of FIND-SYSTEM · 107968bd
      Eric Timmons authored and Robert Goldman's avatar Robert Goldman committed
      FIND-SYSTEM may cause the system to be loaded from the file
      system. REGISTERED-SYSTEM won't load it from the file system, but will return
      something from the file system if it's already been loaded from there.
      
      It's safe to do this as the preloaded systems are always considered to be
      registered.
      107968bd
    • Eric Timmons's avatar
      7f86b8fc
    • Eric Timmons's avatar
      Add failing test for #94 · 40697872
      Eric Timmons authored and Robert Goldman's avatar Robert Goldman committed
      40697872
    • Eric Timmons's avatar
      Fix test-mutual-redefinition.script · 2a565c48
      Eric Timmons authored and Robert Goldman's avatar Robert Goldman committed
      Since 3.3.2 / 069cd2a6, the primary system name
      of a misnamed system is derived from the pathname of the .asd file that defines
      it, not the name of the system itself. This means that within the same cache
      session, any operation on a misnamed system will depend on DEFINE-OP for the
      file where it was already found and will *not* depend on a DEFINE-OP for the
      "syntactic" primary name.
      
      The test test-mutual-redefinition.script has been broken since (at least)
      then. However, it was missed due to UPGRADE-ASDF always returning T. This
      resulted in every load-system in this test running with an isolated cache.
      2a565c48
    • Eric Timmons's avatar
      In CLEAR-CONFIGURATION-AND-RETRY restart, clear the session cache only if it exists · 37861104
      Eric Timmons authored and Robert Goldman's avatar Robert Goldman committed
      An effect of UPGRADE-ASDF always returning true is that a nested session was
      unconditionally started by the :AROUND method on OPERATE. This means
      that *ASDF-SESSION* was always bound to a session object whenever any real work
      was being done.
      
      Now that UPGRADE-ASDF does not unconditionally return T, it's likely that
      CLEAR-CONFIGURATION-AND-RETY will be invoked in the first
      CALL-WITH-ASDF-SESSION on the stack and *ASDF-SESSION* will be bound to
      NIL. So, check that it's not NIL before we grab its SESSION-CACHE.
      37861104
    • Eric Timmons's avatar
      make UPGRADE-ASDF return T only if a version number changed · 2bd1b0b4
      Eric Timmons authored and Robert Goldman's avatar Robert Goldman committed
      This is what the docstring says it does. However, it's unconditionally returned
      T since 2.27 / ab797258.
      2bd1b0b4
  6. 24 Dec, 2021 3 commits
    • Robert Goldman's avatar
      Bump version to 3.3.5.4 · 10cd02ce
      Robert Goldman authored
      10cd02ce
    • Robert Goldman's avatar
      Merge branch... · 9bd4ae14
      Robert Goldman authored
      Merge branch '98-uiop-define-package-signals-a-type-error-when-trying-to-import-from-a-non-existent-package' into 'master'
      
      Resolve "UIOP:DEFINE-PACKAGE signals a TYPE-ERROR when trying to IMPORT-FROM a non-existent package"
      
      Closes #98
      
      See merge request !197
      9bd4ae14
    • Robert Goldman's avatar
      Better error message for import-from in define-package. · 1731a174
      Robert Goldman authored
      Resolve "UIOP:DEFINE-PACKAGE signals a TYPE-ERROR when trying to IMPORT-FROM a non-existent package" (#98)
      
      The code handling other options to `define-package` used `find-package*`, 
      which (by default) errors if it can't find the package it's looking for.  The
      exception was the code for `:import-from`. This caused cryptic error messages
      (issue #98) when trying to import from a package that did not exist.
      
      Switched to using `find-package*`, added a new exception class, and added a test.
      
      1731a174
  7. 23 Dec, 2021 2 commits
  8. 04 Oct, 2021 3 commits
  9. 30 Aug, 2021 1 commit
  10. 27 Aug, 2021 2 commits
  11. 26 Aug, 2021 3 commits
  12. 24 Aug, 2021 4 commits
  13. 27 Jul, 2021 3 commits