libera/#sicl - IRC Chatlog
Search
15:29:55
pjb
An array that is not an array (it has no dimension), containing a number that is not a number! (read-from-string "#0A1D+-0") #| --> #0A1D+-0 #| not-a-number |# ; 8 |#
21:40:20
mfiano
beach: How do you normally subscribe to changes in the model from the view, in a sophisticated CLOS-based application? I am mainly talking about "problem 1" in section 2.1 of the "Using Stealth Mixins to Achieve Modularity" paper (the paper only addresses the "problem 2"). I have considered the observer pattern, but that loosely couples the view in the model, and such mutual dependency circularities
21:40:23
mfiano
make me upset. I am just curious what other options there are, as I've been really thinking on how to make my code more modular lately.
3:05:16
beach
mfiano: I don't have access to the paper, so you need to describe the problems in addition to enumerating them.
3:06:09
mfiano
in summary, the view layer needs to compute some information about the various objects of the model, and store this information for later use. problem 1 is the view subscribing to any modifications in the model, so that these annotations can be
3:07:06
beach
Wouldn't the view then just define an :AFTER method specialized to the stealth mixin class?
3:08:35
mfiano
I don't understand. The stealth mixin paper assumes the reader finds a solution to this problem before stealth-mixins is of use
3:09:08
beach
Oh, sorry, I haven't had my coffee yet. You want to know how this is done without stealth mixins?
3:09:40
mfiano
No, I want to know a solution to the prerequisite discussed that stealth-mixins requires
3:14:27
beach
Well, I don't know of any acceptable solution to the problem without stealth mixins, but the traditional way is the observer pattern.
3:15:14
beach
But, like I said, with stealth mixins, you can then stick an :AFTER method on the operations you want to observe, specialized to the mixin class.