[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Translator and R5RS
From: |
Keisuke Nishida |
Subject: |
Re: Translator and R5RS |
Date: |
06 Oct 2000 20:30:24 -0400 |
User-agent: |
T-gnus/6.14.4 (based on Gnus v5.8.6) (revision 02) SEMI/1.13.7 (Awazu) Chao/1.14.0 (Momoyama) Emacs/20.7 (i686-pc-linux-gnu) MULE/4.1 (AOI) |
Michael Livshin <address@hidden> writes:
> > I'm thinking about the design of a new compiler for my VM, which works
> > in 3 steps:
(snip)
> looks good, except I don't really understand why macro expansion
> should be done in the "translate" phase. indeed, the "read" and
> "translate" phases are begging to be one phase, unless I'm missing
> something. I mean, what language needs the Scheme macro facility
> except for Scheme itself?
I was thinking that, even in the same Scheme, there are some minor
differences in people's syntactic preference. For example, "foo.bar"
is a symbol foo.bar in R5RS, while I'd like it if it is expanded into
(bar foo). Hmm, maybe this should be controlled by a reader option,
and I don't need to separate the two phases.
> also, unrelatedly, perhaps you could try to make your new compiler
> (the "translate" phase at least) support some extendable GOOPS'y
> protocol, so people could plug in new optimizations and stuff.
Right. I'll try.