Commit 95d7324b authored by Robert P. Goldman's avatar Robert P. Goldman
Browse files

Sucked Fare's slide on upgrading up into the appropriate place in the outline.

parent 2a469490
......@@ -257,6 +257,29 @@ sub-bullet under a major header.
**** While it is running /to build and load itself/
**** COMMENT image of snake eating its own tail...
** Hot-patching: how to do it
*** Mostly easy: upgrading data, with =update-instance-for-redefined-class=
**** "pull" model: everything sees the new schema. No "push" stages.
*** Hard: changing a function's signature
**** CLOS won't even let you do it.
*** Rebinding (=fmakunbound=) vs Shadowing (=unintern= in all packages)
**** No "rebind to transitional version that wraps the new version, then shadow"
*** Harder: modified functions are in the continuation of =compile-file= or =load=
**** Can't update continuation frames; they have no first-class names to be rebound.
**** Worse if multithreaded: no atomicity
* Configuration
** COMMENT 4 slides here
** Configuring ASDF
......@@ -468,27 +491,6 @@ sub-bullet under a major header.
**** thou shalt tailor thy datastructures to the target problem
**** Without the test suite, we'd be nowhere.
** Upgrading ASDF
*** Mostly easy: upgrading data, with =update-instance-for-redefined-class=
**** "pull" model: everything sees the new schema. No "push" stages.
*** Hard: changing a function's signature
**** CLOS won't even let you do it.
*** Rebinding (=fmakunbound=) vs Shadowing (=unintern= in all packages)
**** No "rebind to transitional version that wraps the new version, then shadow"
*** Harder: modified functions are in the continuation of =compile-file= or =load=
**** can't update continuation frames; they have no first-class names to be rebound.
**** Worse if multithreaded: no atomicity
** What is still wrong with ASDF
*** no side-effect isolation
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment