freenode/#sicl - IRC Chatlog
Search
12:54:53
beach
But client code can change it, because the code generated depends on the implementation.
14:11:34
beach
So in bootstrap environment E3, I introduced a special version of ADD-METHOD, and now I suffer the consequences. I did it out of laziness, I guess. I couldn't face dealing with all the dependencies to make that work. On the other hand, I didn't really check the extent of those dependencies. I just did the simplest thing I can think of.
14:12:25
beach
I kind of relied on satiation to fix things up, but now I have removed satiation entirely from the bootstrapping procedure, so my special version is no longer appropriate.
14:14:35
beach
One thing I should definitely do is split up ADD-METHOD into its different components.
14:14:38
beach
One component searches for an existing method with the same specializers and qualifiers and removes it if it exists.
14:15:28
beach
Another component updates the specializer profile to account for parameters that might not have been specialized before, but that are now with the new method.
14:16:48
beach
The main component goes through the call history and checks whether the new method is applicable to any history entry, and if so, removes that entry.
14:20:45
beach
By splitting it up into components, I might get away with redefining only *some* components at bootstrapping time, whereas now, my only choice is to either make the entire thing work as it is, or provide a special version for the entire thing.