freenode/#sicl - IRC Chatlog
Search
18:38:26
heisig
I agree that there should be separate protocols for global environments and for lexical environments.
18:39:07
heisig
However, every global environment should also be a valid lexical environment - the null lexical environment.
18:40:42
heisig
Which, luckily, shouldn't be too hard. One can just implement the Trucler protocol with the global environment protocol.
18:41:57
heisig
One for global environments, that is not concerned with lexical environments at all.
18:42:36
heisig
And a second one - Trucler - that weakly depends on the former and provides access to the lexical environment.
18:43:26
heisig
With the small extra feature that Trucler will handle any augmentation function on a global environment by returning a lexical environment.
18:45:58
Bike
i feel like an augmentation function would probably be insensitive to the nature of the parent anyway
18:49:20
heisig
The global environment could also provide a native-client, similar to Trucler. It would be much easier to write, because it can just use SYMBOL-FUNCTION, FBOUNDP and the like.
18:52:17
heisig
Another fun thought: Once I finish trucler-native, can I use it to write a portable version of EVAL?
4:25:01
ck_
beach: [no action needed on your part] I did most of what we discussed about the floating printer (good thing too, because it revealed a bug in the clhs-conforming code). I didn't touch the variable names, but put in some documentation strings instead. If you ever use it, I'd like to know :)
4:29:13
ck_
beach: so like I told the mcclim people, I'd like to say thanks to you as well. Not everyone is so welcoming.
4:33:46
ck_
You said, if I recall, in #lisp that "by end of year" is the current planning for an executable sicl?
4:34:23
beach
Yes, I just wanted enough time, but still push myself a bit. And I needed a well defined date.