From: Clinton Ebadi <clinton@unknownlamer.org>
Subject: Re: Interested in working on a parser generator
Date: Wed, 3 Sep 2003 19:52:49 -0400 [thread overview]
Message-ID: <200309031952.57639.clinton@unknownlamer.org> (raw)
In-Reply-To: <3F552736.6030707@free-expression.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 02 September 2003 19:26, Lynn Winebarger wrote:
> John Stracke wrote:
> > The FSF's help-wanted page says that a parser generator that generates
> > Scheme would be a welcome utility, for creating Foo-->Scheme
> > translators. I'd be interested in working on such a project; is anybody
> > working on one already?
>
> I wrote the core of a scanner generator this weekend that I could
> donate. It produces a DFA as a big letrec with tail-recursive functions
> for the states.
> Plus it allows you to insert actions with arbitrary scheme code and
> gives you access to the fail and success continuations, even after
> conversion to a dfa (though it does mean the search is breadth-first
> instead
> of depth-first, so you would have to keep track of things with that
> in mind).
> It doesn't have much in the way of error-handling, and contains
> some Chezisms (generic ports and record-case). Also, it only handles
> pre-parsed regular expressions.
> Still, I'm pretty stoked about it. What do I need to do to submit it?
I think that you should publish the code somewhere so that everyone can take a
look. The main Guile developers seem to all be really busy right now (rlb has
a job, Marius is working on some grad school work, etc.) so it could be a
while before anyone would get you the papers to assign copyright to the FSF.
Having the code available would also help others to make it work with Guile
(e.g. put it into a module, say (parser dfa), and then rewrite the Chez
specific code to use the Guile equivalents). I may be able to help with that
(and am entirely willing to assign copyright to the FSF), but I don't know
much about parsers or Chez.
- --
http://unknownlamer.org
AIM:unknownlamer IRC:unknown_lamer@freenode#hprog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/Vn7XdgGh8PQDV0sRAov7AKCNL0avC9N1PgkUAkpFWfK5jjTYHgCcC0re
rVLuNIdYvb+zF4hSmPjccCI=
=TQco
-----END PGP SIGNATURE-----
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-09-03 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 0:02 Interested in working on a parser generator John Stracke
2003-09-02 23:26 ` Lynn Winebarger
2003-09-03 23:52 ` Clinton Ebadi [this message]
2003-09-12 23:19 ` Rob Browning
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=200309031952.57639.clinton@unknownlamer.org \
--to=clinton@unknownlamer.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).