libera/#sicl - IRC Chatlog

2:46:26 beach I was wrong of course. Some off-line thinking and a good night's sleep was needed. I need to read up on everything that was said, but basically the modularity argument is right, and my scenario will be handled by COMPILE-FILE in the user environment being defined as (COMPILE-FILE-IN-COMPILER-ENVIRONMENT :VERBOSE *COMPILE-VERBOSE* ...)

2:47:46 beach Today, I still need to fully understand why using the cell as a key fails in SICL bootstrapping. Once I do, I will plan the (now relatively modest) changes to Maclina that I need to make it work for SICL bootstrapping.

2:50:49 beach bike: SICL has been using not an interpreter of Cleavir ASTs, but a CPS-based compiler of Iconoclast ASTs. The resulting CPS program was so large that SBCL's compiler croaked. So I have been using SBCL's interpreter to evaluate those CPS programs.

3:01:08 bike iconoclast. right.

8:04:05 beach bike: I still don't understand exactly how it works, and at some point, I would like you to walk me through the steps the machine takes and what global cells are gotten from which environment, and how that is done.

8:04:06 beach So in one environment E1, I have code in some function (say F) that (simplified) does (LET ((*SOME-VARIABLE* ...)) *SOME-VARIABLE*). Then I call F from a function G in a different environment E2. Evaluation takes place in environment E2. What global cell for *SOME-VARIABLE* is used when that variable is bound, and what global cell for it is used when its value is asked for?

8:04:45 beach This code fails because *SOME-VARIABLE* is not bound in the body of the LET.

8:05:22 beach bike: I realize you are not awake, and I have to be somewhere else in a little while. So no rush. When you are awake and you have time.

8:08:19 beach Since the symbol *SOME-VARIABLE* is not at all involved in environment E2, I can't figure out why a global cell from E2 would be involved at all either.