<paroneayea>amz31: I was thinking about what I said earlier about the actor model being a good fit for something like dwarf fortress <paroneayea>if you want it to be deterministic, and controlled by each tick <paroneayea>which is nice when you have async environments where things can handle stuff when they get to it <paroneayea>but something like dwarf fortress is closer to cellular automata <paroneayea>maybe the propagator model would be a good fit, I really don't know <koosha>why isn't there the converting procedures available in guile ? <mark_weaver>koosha: there are many conversion procedures in guile, but your question is too vague to make sense of. can you be more specific? <koosha>mark_weaver: Yes , sorry . As an example : (char->integer #\\c) <koosha>mark_weaver: It goes to next line and wants input . <koosha>Stupid mistake from me . Sorry ! ***amz31 is now known as amz3
<amz3>paroneayea: ok thx for the info <amz3`>paroneayea: thx again for the advice, I had a look at celullar automata, but I think I will dive into propagator first, I think it will more fun, that said I invested a lot of time in my search engine, so I think I will make that work first <amz3`>paroneayea: also don't hesitate to share your findings regarding propagators ***Fuuzetsu_ is now known as Fuuzetsu
<roelj>In Common Lisp, there's a `break' to debug code. Is there an equivalent function in Guile Scheme? <wingo>it would be nice if we had such a thing and it were well defined <roelj>Is there a way I can set a breakpoint from Scheme code for the Guile interpreter? <wingo>to actually do it within the context of the error <wingo>(use-modules (system repl repl) (system repl debug)) <wingo>(start-repl #:debug (make-debug (make-stack #t) 0 "my special debug")) <wingo>you can keep both pieces, etc etc <roelj>wingo: Thanks! No wonder I couldn't find it in the manual :) <wingo>roelj: it is possible to set a breakpoint tho <wingo>search the manual for "break" <wingo>,break-at-source is the repl command <roelj>Yes, but that's from the REPL, not from the code <wingo>programmatically setting breakpoints is wizardry and i think you are expected to dig a bit :) <wingo>see "High-Level Traps" in the manual tho <wingo>there is add-trap-at-source-location! <paroneayea>ACTION just throws exceptions when he wants to explore and wraps everything in (pk) ;) <ijp>today I decided that I really need a pklet for tracing named lets