From: Matt Wette <matt.wette@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: nyacc version 0.71.0 released
Date: Tue, 21 Jun 2016 11:12:09 -0700 [thread overview]
Message-ID: <C5634AC2-6365-426C-8B2E-3A44909D0CC9@gmail.com> (raw)
In-Reply-To: <87vb127fr9.fsf@gnu.org>
> On Jun 21, 2016, at 7:55 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Matt Wette <matt.wette@gmail.com> skribis:
>
>> nyacc version 0.71.0 is released as beta
>>
>> nyacc is a LALR parser generator written from the ground up in guile
>>
>> Features/Updates:
>> * clean scheme-flavored syntax for grammar specification
>> * prototype parsers for C99,(partial) javascript, matlab that output parse trees in a SXML format
>> * update: C99 preprocessor updated to expand defines in C code
>> * update: cleaned up file structure
>> * update: started working on test-suite
>> * update: added grammar for C++
>
> Very impressive!
>
> Side note: it would be nice if there were a tiny configure.ac and
> Makefile.am to simplify build and installation. :-)
Thanks. Getting C++ and Javascript fully working is going to be a lot of work: C++ needs backtracking and Javascript needs “pruning”. But the C99 parser is mature enough to provide some value, I think.
Regarding using autoconf, I was hoping to minimize overhead code. If the lone Makefiles are not cutting it I can work to blend in autoconf.
Irrelevant side note: Years ago I developed a tool like automake, called metamake, that provided macros, implemented in M4, to expand “makefile.mm" into “makefile". To this day automake just seems to me like the wrong way to do that job.
Matt
next prev parent reply other threads:[~2016-06-21 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 20:49 NYACC version 0.70.0 released Matt Wette
2016-04-15 1:47 ` nyacc version 0.71.0 released Matt Wette
2016-06-21 12:21 ` Chaos Eternal
2016-06-21 12:55 ` Matt Wette
2016-06-21 13:21 ` Matt Wette
2016-06-21 14:55 ` Ludovic Courtès
2016-06-21 18:12 ` Matt Wette [this message]
2016-06-22 7:34 ` Chaos Eternal
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=C5634AC2-6365-426C-8B2E-3A44909D0CC9@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).