unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: bolega <gnuist006@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: C interpreter in Lisp/scheme/python
Date: Tue, 13 Jul 2010 23:01:39 -0700 (PDT)	[thread overview]
Message-ID: <9969f3c0-73e3-48e8-b4df-734c64bd00c0__40263.4894628592$1291845198$gmane$org@t10g2000yqg.googlegroups.com> (raw)
In-Reply-To: hvmpuc$2s4$2@speranza.aioe.org

On Jun 20, 9:31 pm, Richard Fateman <fate...@cs.berkeley.edu> wrote:
> Define Macro wrote:
> > On Jun 13, 7:07 pm, bolega <gnuist...@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



  parent reply	other threads:[~2010-07-14  6:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e1aa09cd-3bcd-4e9b-8f4c-e307a14246fe@a2g2000prd.googlegroups.com>
2010-06-14  0:15 ` C interpreter in Lisp/scheme/python Vinay
2010-06-14 10:57 ` Albert van der Horst
2010-06-14 13:25 ` fortunatus
     [not found] ` <f0b3e0c2-2099-4808-9724-b64452a9e747@w12g2000yqj.googlegroups.com>
     [not found]   ` <28b50375-3331-4717-bb9e-b7f795fe3d76@j4g2000yqh.googlegroups.com>
2010-06-20  1:48     ` Tim Rentsch
     [not found]     ` <kfnzkyqcw4j.fsf@x-alumni2.alumni.caltech.edu>
2010-07-07 17:00       ` wolfgang.riedel
2010-06-21  1:04 ` Define Macro
     [not found] ` <jwvaaqxcxxt.fsf-monnier+gnu.emacs.help@gnu.org>
2010-07-07 13:50   ` Richard Bos
     [not found] ` <5032d354-3017-45c2-b4f3-417457ac5247@z8g2000yqz.googlegroups.com>
     [not found]   ` <e681612a-4527-4991-8f0f-6dbf94a96510@5g2000yqz.googlegroups.com>
     [not found]     ` <734278b3-f5c0-49b8-a1a1-c54919231631@c10g2000yqi.googlegroups.com>
2010-07-08  8:39       ` Pascal J. Bourguignon
     [not found]       ` <87lj9mfju6.fsf@kuiper.lan.informatimago.com>
2010-07-08 21:13         ` George Neuner
     [not found] ` <e55d65a2-088c-4a0b-ad47-2d0afef487e0@e5g2000yqn.googlegroups.com>
     [not found]   ` <hvmpuc$2s4$2@speranza.aioe.org>
2010-07-14  6:01     ` bolega [this message]
     [not found]     ` <9969f3c0-73e3-48e8-b4df-734c64bd00c0@t10g2000yqg.googlegroups.com>
     [not found]       ` <mailman.715.1279088292.1673.python-list@python.org>
2010-07-15  5:17         ` bolega
     [not found]         ` <16a7e301-2e85-47eb-971e-79acc4e076a6@b35g2000yqi.googlegroups.com>
2010-07-16  2:43           ` Seebs
2010-07-23 13:10           ` francogrex
     [not found]           ` <i2c4bv$ij4$1@news.eternal-september.org>
     [not found]             ` <icqj46lnoaqkdr5igvqi9so62i30cac26o@4ax.com>
2010-07-24  8:56               ` francogrex
     [not found] ` <7xoceao9jx.fsf@ruckus.brouhaha.com>
2010-07-15  5:26   ` bolega
2010-06-13 23:07 bolega

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='9969f3c0-73e3-48e8-b4df-734c64bd00c0__40263.4894628592$1291845198$gmane$org@t10g2000yqg.googlegroups.com' \
    --to=gnuist006@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).