unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: [ANN] nyacc version 0.86.4 released
Date: Sun, 18 Nov 2018 15:57:37 -0800	[thread overview]
Message-ID: <b5fd3b11-e682-8664-1a4f-d24918b260dc@gmail.com> (raw)

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.

---------------------------

Updates for version 0.86.4:
1) Made significant changes to the C99 parser grammar so that it is more
    robust when parsing attribute specifiers - e.g., __attribute__((packed))
2) Changed scripts/compile-ffi.scm so that dependent ffi and associated
    scm files are checked and (re)compiled if outdated
    (needs some work still : sometimes compiles twice)
3) Fixed fh-wrap, fh-unwrap bugs in system/ffi-help-rt.scm
4) Worked misc issues on example language parsers (octave, modelica).

Note: I will now start to work on cleaning up how c99 handles comments.
       The goal is to carry code-comments as attributes in the AST.

Interesting tidbit for YACC hackers: When I added __attribute__ handling
"everywhere" I found that I was getting a number of shift-reduce conflicts.
So I set up a precedence rule that looks something like:
   (prec< 'shift-on-attr "__attribute__" 'reduce-on-attr)
So in productions where I want to shift on "__attribute__" I use a RHS like
   (foo bar ($prec 'shift-on-attr))
and in productions where I want to reduce on "__attribute__" I use a RHS like
   (foo baz ($prec 'reduce-on-attr))
where RHS = "right hand side of production rule"

---------------------------

NYACC maturity is beta 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 guide:
* http://www.nongnu.org/nyacc
* https://savannah.nongnu.org/projects/nyacc
* http://www.nongnu.org/nyacc/nyacc-ug.html

For support see:
     https://savannah.nongnu.org/support/?group=nyacc





                 reply	other threads:[~2018-11-18 23:57 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=b5fd3b11-e682-8664-1a4f-d24918b260dc@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).