From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: [ANN] nyacc 1.00.1 released
Date: Sun, 29 Dec 2019 14:56:49 -0800 [thread overview]
Message-ID: <6c4bd578-46dd-ed71-fd8b-b9fda50a399b@gmail.com> (raw)
I have released version 1.00.1 of nyacc. This fixes a few issues w/ 1.00.0.
NYACC, for Not Yet Another Compiler Compiler, is set of guile modules for
generating parsers and lexical analyzers. It also provides sample parsers
and pretty-printers using SXML trees as an intermediate representation.
It provides a decent C parser and a `FFI Helper' tool to help create
Guile Scheme bindings for C-based libraries.
It provides (partially implemented) compilers based on above mentioned
parsers to allow execution with Guile as extension languages.
changes in 1.00.1 with respect to 1.00.0:
* restored code that was commented-out in 1.00.0, so now
#if FOO
works again when FOO is not defined
* in nyacc/util.scm, changed a letrec* to letrec
* in nyacc/lang/util.scm, changed a letrec* to let*
* updated all Makefile.in for autoconf conventions, using
abs_top_builddir and abs_top_srcdir
* added test-suite/Makefile.in to replace lower level versions
NYACC maturity is production/stable level.
NYACC is free software; the full source distribution is available through
* the tarball repository:
https://download.savannah.gnu.org/releases/nyacc/
* the git repository:
git://git.savannah.nongnu.org/nyacc.git
home page, project page and user's guides:
* https://www.nongnu.org/nyacc
* https://savannah.nongnu.org/projects/nyacc
* https://www.nongnu.org/nyacc/nyacc-ug.html
* https://www.nongnu.org/nyacc/ffi-help.html
Report bugs:
* https://savannah.nongnu.org/bugs/?func=additem&group=nyacc
Get support:
* https://savannah.nongnu.org/support/?group=nyacc
reply other threads:[~2019-12-29 22:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6c4bd578-46dd-ed71-fd8b-b9fda50a399b@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@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).