22:50:48aethI think the only way to have useful BF as a compilation target is to move the world around some central area (so it's always close by) as you walk through the BF tape. Or perhaps have two BFs talk to each other.
22:51:19aethDefinitely not a worthwhile use of time to build Lisp on that.
22:51:53rmeccl rebuilds itself in 30 seconds on my iMac.
22:53:37aethAn extended macro system could probably do something very similar to what C++ does in a Lisp without the massive time penalties of C++ compilation.
22:55:28Bikehow does ccl build, anyway? i've never been quite clear
23:01:14rmeIt bootstraps by writing a minimal image file (which it constructs in memory), and alsocompiling (or cross-compiling) additional source files that comprise the rest of the lisp. You can then start the bootstrap image, which will then load those fasl files. Then you save an image of the lisp you just made.
23:17:35rmeI don't think the existing bootstrapping process is totally insane.
23:21:03phoerme: I mean "sane" as "not needing a CCL before it".
23:21:29phoeI looked at CCL's bootstrapping process some time ago and I wouldn't call it mad, if that's what I accidentally implied.
23:21:46phoeBut yes, it's time for me to go to sleep.
23:22:09Xachxof just called it sanely bootstrappable for a cute pun
23:24:17aethAhah! At least in SBCL, I can do this: (deftype false () `(member :false)) and then these are essentially identical: (defun foo (x) (typep foo 'nil)) (defun foobar (x) (typep x 'false))
23:26:25aethAhah! At least in SBCL, I can do this: (deftype false () `(member :false)) and then these are essentially identical: (defun foo (x) (typep foo 'null)) (defun foobar (x) (typep x 'false))
3:19:37jcowanperhaps sbcl stands for sanely bootstrappable common lisp, at least some of the time?
3:42:03k-hospretty sure it stands for salty bacon common lisp