From: Matt Wette <matt.wette@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Guile User Mailing List <guile-user@gnu.org>,
guile-devel <guile-devel@gnu.org>
Subject: Re: [ANN] nyacc 0.82.1 released
Date: Sat, 11 Nov 2017 07:22:15 -0800 [thread overview]
Message-ID: <6057A351-2C14-4047-AC03-B5D30DB25948@gmail.com> (raw)
In-Reply-To: <878tfcyjp8.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
> On Nov 11, 2017, at 6:27 AM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>
> Matt Wette writes:
>
> Hey Matt,
>
>> Nyacc 0.82.1 has been released.
>
> Congrats!
>
> It's been a while but in 0.82.0 I found a regression of a bug that you
> fixed earlier, I think in 0.80.4
>
> https://lists.gnu.org/archive/html/guile-user/2017-06/msg00003.html
>
> I've attached the problematic file again. It's also still present in 0.82.1
>
> $ guile
> GNU Guile 2.2.2
> Copyright (C) 1995-2017 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(guile-user)> (use-modules (nyacc lalr))
> scheme@(guile-user)> *nyacc-version*
> $1 = "0.82.1"
> scheme@(guile-user)> (use-modules (nyacc lang c99 parser))
> scheme@(guile-user)> (with-input-from-file "def-bwl.c" parse-c99)
> (unknown):1: parse failed at state 89, on input "DEF_BWL"
> (unknown):1: C99 parse error
> $2 = #f
Ugh. I thought I had that one. I will take a look
PASS: nyacc/c99-01, CPP: #, ##, __VA_ARGS__
[-- Attachment #2: Type: text/html, Size: 2961 bytes --]
prev parent reply other threads:[~2017-11-11 15:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDFB9E11-6781-4F31-A654-4C644350CA4F@gmail.com>
2017-09-10 15:37 ` [ANN] nyacc 0.82.0 released Matt Wette
2017-09-10 18:17 ` Matt Wette
2017-09-12 1:44 ` Matt Wette
2017-09-16 16:53 ` [ANN] nyacc 0.82.1 released Matt Wette
2017-11-11 14:27 ` Jan Nieuwenhuizen
2017-11-11 15:22 ` Matt Wette [this message]
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=6057A351-2C14-4047-AC03-B5D30DB25948@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-devel@gnu.org \
--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).