libera/#clasp - IRC Chatlog
Search
13:16:44
Bike
so far today i've just been frustrated trying to sign into kronos, but yeah, hopefully can try putting it in clasp now
13:27:01
Bike
which i thought i was having trouble starting, but i guess you need to do -I -n and not -In
13:36:24
drmeister
You might want to also add -f clasp-min. There is stuff in that code that is available only when loaded the first time.
13:38:26
Bike
stopped almost immediately because it can't find set-documentation, wtf... i'll try clasp-min
13:46:41
Bike
it was trying to bytecode-compile the definition of with-interpreter in cmprepl, i think.
13:48:21
Bike
the cmprepl-bytecode i'm using is pretty much like yours, cept with-interpreter i guess
13:49:36
Bike
pushed to vm. it's bytecode-compile.lisp and cmprepl-bytecode.lisp. but as mentioned this typecase thing will kill them
14:08:25
drmeister
FYI clasp/src/lisp/kernel/init.lisp is also being loaded right at the start - that was turning off *load-print*
14:08:27
Bike
it doesn't look like an infinite recurison to me, but it's hard to tell because as soon as it tries to print a bytecode compiler environment it crashes, because they're full of circularities
14:10:25
drmeister
Ok, then if you want to evaluate things a little more slimey you can use M-x run-lisp and give it iclasp-boehmprecise -I -f clasp-min -l loader.lisp
14:11:07
drmeister
I think <Shift>-<Enter> on a form in a buffer will pass that form to the run-lisp *interactive-lisp* buffer
14:11:17
Bike
the backtrace says that (var-info nil [an environment]) somehow immediately calls bytecode-implicit-compile-repl-form, which seems nonsensical
14:12:16
drmeister
Once you install (setq *implicit-compile-hook* 'bytecode-implicit-compile-repl-form)
14:12:53
drmeister
If you leave *implicit-compile-hook* alone - then you can use the clasp interpreter to evaluate things.
14:13:50
Bike
i mean, it's saying that the function var-info somehow calls the implicit compile hook
14:16:58
drmeister
I would turn on *load-print* and load the source code and see what expressions cause it to fail.
14:17:37
drmeister
Then don't load cmprepl-bytecode.lisp and bytecode compile that last expression in a run-lisp session.
14:20:27
Bike
Alright, so with that done i can see it gets all the way to... uh... itself, actually, to bytecode-compile.lisp
14:20:59
drmeister
Edit cmprepl to set *implicit-compile-hook* to the bytecode compiler/interpreter, hit a problem, unset it, load- that code and then try and bytecode compile and run it.
14:22:15
Bike
i already hooked bytecode environments into macro-function and stuff, but in this case it's load _constructing_ an environment and passing that to the bytecode compiler, rather than the other way around
14:22:57
Bike
well, it's fine, i can translate a clasp macrolet environment into a bytecode compiler one, as long as there are a few basic accessors
14:24:19
Bike
actually i really don't understand what's even making this macrolet environment, so let me find that first
14:26:40
drmeister
~/Development/clasp-vm/build/boehmprecise/iclasp-boehmprecise -I -f clasp-min -l ~/Development/clasp-vm/bloader/loader.lisp
14:26:48
Bike
i see, and eval-with-env-hook goes to t1evaluate, so it will try to do its own thing with toplevel forms before dropping to the implicit compile hook
14:27:45
Bike
so either i translate interpreter environments, or maybe i can just replace eval-with-env-hook? is there a reason i shouldn't?