ASDF uses CHANGE-CLASS because (1) it caches a system's identity before it's defined (2) re-loading can cause changehttps://twitter.com/juhosnellman/status/625712153891315713 …
-
-
Replying to @fare
@fare What's the relation between CHANGE-CLASS and UPDATE-INSTANCE-FOR-REDEFINED-CLASS? I read this earlier today: http://malisper.me/2015/07/22/debugging-lisp-part-3-redefining-classes/ …1 reply 0 retweets 0 likes -
Replying to @duncanmak
They are both features of the CLOS MOP. ASDF relies on U-I-F-R-C when it is upgraded and its internals changed.
@duncanmak1 reply 0 retweets 0 likes -
Replying to @fare
U-I-F-R-C is a feature of live systems that remain up as change happens, as opposed to dead systems that restart from scratch every time.
3 replies 0 retweets 2 likes -
Replying to @fare
CL code upgrade issues: no transactions; unclear inline (default) function call semantics; no U-I-F-R-C for stack frames.
1 reply 0 retweets 0 likes
code-upgrade friendly: transactions; virtualization; syntax distinction b/w static&dynamic calls (like erlang). U-I-F-R-C for stack frames?
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.