Inline!

On Aug 19, 2012, at 3:47 PM, Ian Piumarta <[email protected]> wrote:

> Hi Shawn,
> 
>> My starting point was the published sources for Maru 2.1 here:
>> http://piumarta.com/software/maru
> 
> Thanks for posting this.
> 
> Your issues with %typecheck, <header> and <buffer> were due to generating the 
> evaluator with %define-accessors set to %define-safe-accessors in boot.l.  
> Setting %define-accessors to %define-unsafe-accessors fixes them.

Yes, playing it safe ends up in the middle of the road, which isn't safe at 
all.  

> Your other observations arising from bit rot were spot-on and I've updated 
> the sources and made a maru-2.2 tarball that can generate a working evaluator 
> from emit.l and eval.l.  I took the liberty of writing subr_read from 
> scratch, to match the one in eval.c, and updated various other things to 
> better match the current features.

Fantastic! Maru is really lovely and new bits are awesomesauce.

> Although 'make test' and 'make test2' are working again, the languages 
> implemented by eval.c and eval.l are slightly different due to development in 
> the former that has not been carried forward into the latter.

That's funny and fascinating. The bootstrap is not evolving alongside the 
bootstrapped thing. What's funny is that it can still bootstrap, and is still 
metacircular, while the prototype sits around collecting dust. It's kind of 
like the smoldering mess that's left after a rocket leaves for the moon. Good 
work!

> Regards,
> Ian

I'm really pleased to see that Maru still lives. No BCPL clone? Is Maru "it" at 
this point? Feel free of course to decline to comment on this paragraph until 
the time is right. 

P.S.

You mentioned something about a generation scavenging GC for it, did you do 
that? 'Cause if you did we might have a the roots of a fast (enough) Lisp 
that's purer than Scheme. 

'Scuse the French, but holy shit. 

--Casey
_______________________________________________
fonc mailing list
[email protected]
http://vpri.org/mailman/listinfo/fonc

Reply via email to