8:38:35nmz787so I'm not sure whether to use the clasp latest, or the clas 0.5 instructions here https://github.com/clasp-developers/clasp/wiki/Build-Instructions
8:38:48nmz787I already cloned cando into the extensions folder
8:38:52kpoeckI use the dev branch, might also be worth a try
8:41:35kpoeckI i ditched externalclasp for llvm501
8:47:56kpoeckI strongly believe that you don’t need external clasp on linux
8:48:25kpoeckI know i don’t even need it on Darwin
12:13:46Kevslinger::notify nmz787 the condition.h error is caused when you're in cando's master branch. Make sure you use both clasp's and cando's dev branch for building.
12:13:46ColleenKevslinger: Got it. I'll let nmz787 know as soon as possible.
13:49:50Shinmerascymtym: Could you add an explicit check for the package in eclector-reader:interpret-symbol that signals an eclector-specific condition as well as a restart to spoof the symbol? I'd like to be able to chuck code snippets that refer to unknown packages.
13:50:22ShinmeraRight now it relies on an implementation-defined condition for the package error, which makes it hard to write this portably, and there's no restart to insert another symbol or value in its place on error.
14:26:06scymtymShinmera: my current plan is adding a "client" parameter to INTERPRET-{TOKEN,SYMBOL} so that the client gets full control if desired. i think that also work for your case. what do you think?
14:28:05scymtymbeach: should i postpone such changes until you finish the second climacs experiment?