Re: Syntax directed compilation

"Matthew X. Economou" <xenophon+usenet@irtnog.org>
31 May 2007 11:19:40 -0400

          From comp.compilers
Related articles
Syntax directed compilation barry.j.kelly@gmail.com (Barry Kelly) (2007-05-26)
Re: Syntax directed compilation ang.usenet@gmail.com (Aaron Gray) (2007-05-28)
Re: Syntax directed compilation sdn@svpal.org (Steven Nichols) (2007-05-28)
Re: Syntax directed compilation thomas.mertes@gmx.at (2007-05-29)
Re: Syntax directed compilation cfc@shell01.TheWorld.com (Chris F Clark) (2007-05-29)
Re: Syntax directed compilation xenophon+usenet@irtnog.org (Matthew X. Economou) (2007-05-31)
Re: Syntax directed compilation barry.j.kelly@gmail.com (Barry Kelly) (2007-06-20)
| List of all articles for this month |
From: "Matthew X. Economou" <xenophon+usenet@irtnog.org>
Newsgroups: comp.compilers
Date: 31 May 2007 11:19:40 -0400
Organization: NewsGuy - Unlimited Usenet $19.95
References: 07-05-088
Keywords: design, Lisp
Posted-Date: 31 May 2007 15:45:02 EDT

>>>>> "Barry" == Barry Kelly <barry.j.kelly@gmail.com> writes:


        Barry> As far as I can see, the closest living embodiment of the
        Barry> concept is Lisp, but Lisp programs seem not to have
        Barry> explored this particular level of abstraction - viewing the
        Barry> source read by the Lisp interpreter / compiler as being
        Barry> instructions on how to create an executable. Instead, while
        Barry> much macro magic is available, ultimately it only affects
        Barry> the code subsequently read, rather than defining the
        Barry> back-end of a compiler.


I'm not a Lisp expert, but maybe you can prototype something similar
to what you propose with reader macros (especially the read-time-eval
macro "#.") and compiler macros. It might be worth posting your
comments on comp.lang.lisp.


Best wishes,
Matthew

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.