unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Daniel Kraft <d@domob.eu>
To: guile-devel@gnu.org
Subject: Re: Some more elisp aspects: Reader and documentation
Date: Mon, 17 Aug 2009 14:07:10 +0200	[thread overview]
Message-ID: <4A8947EE.4080407@domob.eu> (raw)
In-Reply-To: <87tz06u0gq.fsf@gnu.org>

Hi Ludo,

Ludovic Courtès wrote:
> Sorry for the late reply.

no problem, thanks for the reply!  I had a lot of other stuff to do 
anyways, and so didn't really get into the situation of waiting for a 
reply here ;)

>> 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.

Hm, ok, I'll look into those.  On the other hand I guess that Lisp has 
such a simple syntax that hand-writing some recursive-descent parser may 
be an equally good option?  Well, I'll simply give it a try!

But it seems that the LALR parser generator is part of guile-lib, and 
will introduce that as a new dependency for Guile; do you think that's 
ok?  (Haven't checked how SILex works and if it may introduce dependencies.)

Yours,
Daniel





  reply	other threads:[~2009-08-17 12:07 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
2009-08-17 12:07   ` Daniel Kraft [this message]
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=4A8947EE.4080407@domob.eu \
    --to=d@domob.eu \
    --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).