From: Ken Raeburn <raeburn@raeburn.org>
To: Daniel Kraft <d@domob.eu>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: Elisp Reader
Date: Thu, 27 Aug 2009 22:50:24 -0400 [thread overview]
Message-ID: <D9B0A9D5-99D8-46B8-96A9-57D377E64BB2@raeburn.org> (raw)
In-Reply-To: <4A96BBAD.3000808@domob.eu>
On Aug 27, 2009, at 13:00, Daniel Kraft wrote:
> yesterday and today I implemented the promised elisp reader and just
> pushed the changes. Now Guile's elisp support in my branch should
> be somewhat "complete" because not only there's a compiler but also
> a genuine parser for elisp, handling for instance the [] vectors,
> all those fancy ?\C-\M-x character escape sequences and the syntax
> for circular structures with #n=/#n#. I hope it is fairly complete
> and bug-free, but probably not (as usual) ;)
Fantastic work!
> Feel free to look at it or try it out, I'd be interested to get
> testing results! I could try to run some real elisp code through
> it...
I know where you can find a whole pile of it. ;-)
I assume you don't follow the Emacs development mailing lists...
There's been a little traffic recently about possible multithreading
support and the effect on let-bound buffer-local variables. Not much
discussion so far on the details of the semantics of such cases, but
Tom Tromey is looking into this stuff. (I guess I kind of side-
tracked some of the discussion onto guile-emacs stuff, oops.) Have
you given more thought to buffer-local variables, defvaralias, and
other such headaches? Tom's work and yours aren't quite overlapping,
but you're close....
Ken
prev parent reply other threads:[~2009-08-28 2:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 17:00 Elisp Reader Daniel Kraft
2009-08-28 2:50 ` Ken Raeburn [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D9B0A9D5-99D8-46B8-96A9-57D377E64BB2@raeburn.org \
--to=raeburn@raeburn.org \
--cc=d@domob.eu \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).