freenode/#sicl - IRC Chatlog
Search
16:40:16
jackdaniel
I mean, I was implementing methods from top to bottom, and there was no single place where I had to use funciton-cell (yet), at least as far as function description were going (until I've encountered function-unbound, which description is not clear to me)
16:40:17
beach
You could store the argument to (setf fdefinition) in the function entry, and then copy it to the cell when the cell is asked for, but why the duplication of storage?
16:41:34
beach
I am a bit stressed because dinner is imminent, and I had to connect using a cable which is too short, so I am using the bad built-in keyboard.
16:42:07
beach
So I am reading the code, but I will very likely not understand it before dinner is served.
16:42:48
jackdaniel
function cells in the collection which is used to store functions (and access functions from cells)
16:43:10
jackdaniel
instead of what I did, that is store functions in one collection, and copy them to cells when requested
16:45:01
jackdaniel
you've said, that it is necessary to update function-cell when fdefinition is called, and that surprised me because it was nowhere specified and implementation without doing that works (however not optmially), that's why I have asked
16:47:24
jackdaniel
in light of that, should the specification stipulate that i.e fdefinition updates the function cell? or, if not, how should the specification of function-unbound look like (or should the function be removed)?
17:10:06
jackdaniel
OK, thanks to these missing bits of context now I understand what is the purpose of the function function-unbound. If we specify, that the undefined-function signalling function is stored in the function-cell's cdr, then I think that env:function-unbound is not necessary in the protocol. I'll implement it for now as it is specified.