Eli Barzilay <email@example.com> wrote:
| Arc doesn't share many features of mzscheme, for example: the
| module system, function applications, hygienic macros or any other
| kind of macros (eg, Arc does not have mzscheme's phase separation).
| It doesn't even share mzscheme's namespaces -- in fact, if you look at
| the arc compiler, you'll see that it's lisp-1-ness is not inherited
| from mzscheme, and making it a lisp-2 would be a simple tweak.
Yeah, I was just musing about that -- not making Arc a Lisp-N, but
the other direction: using a Lisp-N (CL) as the backend target of
the Lisp-1 Arc compiler. If one didn't care about the differences
in the underlying semantics [e.g., a different numeric tower than
Scheme], it shouldn't be too hard to port "ac.scm" & "brackets.scm"
to CL, then use them to recompile all the ".arc" files.
Some work would also be needed to replace some of the MzScheme
libraries that get REQUIRE'd; the messiest of those would probably
Rob Warnock <firstname.lastname@example.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607