Skip to content
Snippets Groups Projects
  1. Oct 21, 2011
  2. Oct 20, 2011
  3. Oct 19, 2011
  4. Oct 18, 2011
  5. Oct 17, 2011
  6. Oct 13, 2011
  7. Oct 12, 2011
  8. Oct 10, 2011
  9. Oct 09, 2011
  10. Oct 07, 2011
  11. Oct 06, 2011
  12. Oct 02, 2011
  13. Sep 25, 2011
  14. Sep 14, 2011
  15. Sep 13, 2011
  16. Sep 12, 2011
  17. Sep 02, 2011
    • Robert P. Goldman's avatar
    • Robert P. Goldman's avatar
      New fix for reuse of COMPONENTS based on REINITIALIZE-INSTANCE mehtods. · 97c5462a
      Robert P. Goldman authored
      Thanks to Christophe Rhodes for suggestions.  We use
      REINITIALIZE-INSTANCE to clear out-of-date information out of the slots
      of COMPONENT objects while they are reused.
      
      Two complications presented themselves:
      
      1.  Previously, I believe for orthogonality, we would either get an old
      (reused) COMPONENT or make a new one, but in either case, the handling
      of initargs was done by REINITIALIZE-INSTANCE.  This made it impossible
      for the REINITIALIZE-INSTANCE methods to "know" that they were in a real
      sense RE-initializing.  At the expense of some code duplication, I broke
      this sharing, so that now REINITIALIZE-INSTANCE should only be called
      when we are reusing a COMPONENT, with an exception below...
      
      2.  We always need to have a SYSTEM object active for the defsystem we
      are currently processing.  Accordingly,  SYSTEM objects will *ALWAYS*
      be RE-initialized.  So the REINITIALIZE-INSTANCE method required a
      little care (in particular, the SOURCE-FILE slot needed delicate
      handling.
      97c5462a
    • Robert P. Goldman's avatar
Loading