unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: [ANN] Nyacc version 0.83.0 released
Date: Fri, 6 Apr 2018 17:16:53 -0700	[thread overview]
Message-ID: <702767e4-baef-2b8d-6e88-8b2f2f847e1e@gmail.com> (raw)
In-Reply-To: <874lko8q7v.fsf@gnu.org>



On 04/06/2018 05:38 AM, Jan Nieuwenhuizen wrote:
> Hey Matt,

> I finally got round to looking at it and delighted that everything
> works!  Two patches attached: cond-expands need to grok `mes' (or use
> else instead of `guile').  Also, parsing can be still a bit slow when
> running Nyacc on Mes (tcc.c now parses in ~1h); so I added some tracing
> to stderr.  Possibly you have a better way to do this, esp. the
> NYACC_TRACE environment variable kludge...

I will check out your patches.


> Saw your headsup about changing struct definitions, shall I wait with my
> upcomping Mes 0.12 release for that; do you already have a branch where
> I can test it and change MesCC?

I think it will take me a while to make a release.  I am in the process of
banging on this for a while.  When I get to a good point I will push on
c99dev branch.  I will think about creating another branch for ffi-help dev.

Matt




  reply	other threads:[~2018-04-07  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-21 18:19 [ANN] Nyacc version 0.83.0 released Matt Wette
2018-04-06 12:38 ` Jan Nieuwenhuizen
2018-04-07  0:16   ` Matt Wette [this message]
2018-04-07  0:20   ` Matt Wette
2018-04-07 12:21     ` Jan Nieuwenhuizen

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=702767e4-baef-2b8d-6e88-8b2f2f847e1e@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=janneke@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).