13:43:30drmeisterSo what about using SICL, with its first class global environments, to build cclasp?
13:43:43beachDon't you just need the Clasp macros inside a first-class global environment?
13:44:25Bikewell, we need to run arbitrary code at compile time, right? in a non-host environment
13:44:26drmeisterI think that's what it is - and if macros use macros - they are all clasp macros.
13:44:27beachdrmeister: I don't think SICL is ready for that.
13:45:06beachBike: OK, so you need an EVAL as well.
13:45:45Bikewhich SICL accomplishes by compiling everything to HIR, using a HIR-back-to-common-lisp translator, and then compiling that with the host compiler. right?
13:46:23beachThe Common Lisp code is compiled and then "linked" to the first-class global environment.
13:48:47Bikeif the host supported first class global environments, the code could be evaluated and compiled using the host evaluator/compiler directly with a special build environment, right?
13:54:15Bikekind of the trick here is that a lot of the reason for cross compile would be, rather than build times (which are finicky), maintenance. right now we have bclasp, a full lisp compiler that is only used for building. a lot of code we don't really want to have