From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Some more elisp aspects: Reader and documentation
Date: Mon, 17 Aug 2009 13:46:45 +0200 [thread overview]
Message-ID: <87tz06u0gq.fsf@gnu.org> (raw)
In-Reply-To: 4A7453A2.2020808@domob.eu
Hi Daniel,
Sorry for the late reply.
Daniel Kraft <d@domob.eu> writes:
> 2) Write a seperate elisp reader, possibly in Scheme (but could be C
> as well if that's important for performance). This helps us keep
> "both" readers clean and seperate, but all has to be done from ground
> up and the code is probably slower (when written in Scheme).
This sounds like the best option to me. You could use SILex to build
the lexer (http://www.iro.umontreal.ca/~dube/) and `(text parse-lalr)'
for the parser.
It may be slower than the C counterpart at first but it's bound to get
faster as Andy implements more crazy compiler optimizations. :-)
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-08-17 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 14:39 Some more elisp aspects: Reader and documentation Daniel Kraft
2009-08-17 11:46 ` Ludovic Courtès [this message]
2009-08-17 12:07 ` Daniel Kraft
2009-08-17 12:17 ` Ludovic Courtès
2009-08-17 12:59 ` Daniel Kraft
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=87tz06u0gq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).