C interpreter in Lisp/scheme/python
in [Lisp]
|
Prev: Why warnings about unused keyword although (call-next-method)is used?
Next: Why warnings about unused keyword although (call-next-method) is used?
From: Nick Keighley on 8 Jul 2010 03:10 On 8 July, 08:08, Nick Keighley <nick_keighley_nos...(a)hotmail.com> wrote: > On 7 July, 17:38, Rivka Miller <rivkaumil...(a)gmail.com> wrote: > > Anyone know what the first initial of L. Peter Deutsch stand for ? > > Laurence according to wikipedia (search time 2s) oops! He was born Laurence but changed it legally to "L." including the dot
From: Pascal J. Bourguignon on 8 Jul 2010 04:39 Nick Keighley <nick_keighley_nospam(a)hotmail.com> writes: > On 8 July, 08:08, Nick Keighley <nick_keighley_nos...(a)hotmail.com> > wrote: >> On 7 July, 17:38, Rivka Miller <rivkaumil...(a)gmail.com> wrote: > > >> > Anyone know what the first initial of L. Peter Deutsch stand for ? >> >> Laurence according to wikipedia (search time 2s) > > oops! He was born Laurence but changed it legally to "L." including > the dot Too bad, "Laurence" is a nice name. -- __Pascal Bourguignon__ http://www.informatimago.com/
From: Mark Tarver on 8 Jul 2010 06:27 On 14 June, 00:07, bolega <gnuist...(a)gmail.com> wrote: > I am trying to compare LISP/Scheme/Python for their expressiveness. > > For this, I propose a vanilla C interpreter. I have seen a book which > writes C interpreter in C. > > The criteria would be the small size and high readability of the code. > > Are there already answers anywhere ? > > How would a gury approach such a project ? > > Bolega Probably you want to look at this thread http://groups.google.co.uk/group/comp.lang.lisp/browse_frm/thread/7b1ab36f5d5cce0a/54afe11153025e27?hl=en&lnk=gst&q=minim#54afe11153025e27 where I specified a toy language Minim (much simpler than C) and the goal was to construct an interpreter for it. Similar problem. Many solutions were given in different languages. The thread is very long. One thing you might look at is whether some sort of lexer/parser is supported in any of your targets. Qi supports a compiler-compiler Qi- YACC that allows you to write in BNF which makes this kind of project much easier. See http://www.lambdassociates.org/Book/page404.htm for an overview Mark
From: George Neuner on 8 Jul 2010 17:13 On Thu, 08 Jul 2010 10:39:45 +0200, pjb(a)informatimago.com (Pascal J. Bourguignon) wrote: >Nick Keighley <nick_keighley_nospam(a)hotmail.com> writes: >> Nick Keighley <nick_keighley_nos...(a)hotmail.com> wrote: >>> Rivka Miller <rivkaumil...(a)gmail.com> wrote: >> >>>> Anyone know what the first initial of L. Peter Deutsch stand for ? >>> >>> Laurence according to wikipedia (search time 2s) >> >> oops! He was born Laurence but changed it legally to "L." including >> the dot > >Too bad, "Laurence" is a nice name. He probably hates the nickname "Larry".
From: bolega on 14 Jul 2010 02:01
On Jun 20, 9:31 pm, Richard Fateman <fate...(a)cs.berkeley.edu> wrote: > Define Macro wrote: > > On Jun 13, 7:07 pm, bolega <gnuist...(a)gmail.com> wrote: > >> I am trying to compare LISP/Scheme/Python for their expressiveness. > > >> For this, I propose a vanilla C interpreter. I have seen a book which > >> writes C interpreter in C. > > >> The criteria would be the small size and high readability of the code. > > >> Are there already answers anywhere ? > > Sure. Lots of texts on compilers provide exercises which, in one way or > another suggest how to write an interpreter and perhaps a compiler too > for some language. Anyone taking a course on compilers is likely to > have followed such exercises in order to pass the course. Some > instructors are enlightened enough to allow students to pick the > implementation language. > > Ask any such instructor. Beware, he does not tell the readers the financial details. This is what he wrote to me by email. <quote> I would be willing to meet with you here in Berkeley to educate you on these matters at a consulting rate of $850 per hour, with a minimum of 8 hours. RJF </quote> > I think you will find that many people use a packaged parser-generator > which eliminates much of the choice-of-language difference. Do you like > Bison, Yacc, Antlr, or one of the many parser generators in Lisp, > python, etc. > > My own experience is that in comparing Lisp to C, students end up with > smaller and better interpreters and compilers, faster. I don't know > about python vs C for sure, but I suspect python wins. As for > python vs Lisp, I don't know. > > RJF |