10:19:55rk[ghost]that brings up an interesting thought.. what do you all use for serialization of function objects?
11:08:25_deathgenerally you avoid serializing those.. but see http://www.discontinuity.info/~pkhuong/common-cold/
11:40:26phoegenerally you serialize those by (if at all) capturing their source code at compile time and storing the source code, then compiling it again during deserialization
11:40:52phoesince that's the only semi-portable way that is standard-compliant AFAIK
16:55:14dimbut well CL X11 support seems not to like macosx XQuartz
16:55:37dloweyou could write the macos mcclim backend!
16:56:31dimwell given infinite time sure, I could grow the necessary skill set then do that
16:56:39dimyou'd be bored well before I get there tho
16:57:36rk[ghost]phoe: i like rlwrap sbcl.. but i was trying to use cl-readline to make a custom readline for a internal repl.. (the rlrwap was catching all my keypresses and i couldn't figure out why the lib wasn't working as described:P)
16:59:38rk[ghost]phoe: aye. assuming i make equalized hardware on a distributed system just curious
17:00:09dlowedim: nothing gets done without encouraged people
17:00:34rk[ghost]since serialization is a major concern when designing a good concurrent system, was curious how it handled something high-level like a function