From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] nyacc 0.80.4 released
Date: Fri, 04 Aug 2017 12:31:09 +0200 [thread overview]
Message-ID: <8760e3fwuq.fsf@gnu.org> (raw)
In-Reply-To: <521B54ED-14CD-430D-A109-E9DEAA3DA798@gmail.com> (Matt Wette's message of "Wed, 2 Aug 2017 05:22:03 -0700")
Matt Wette writes:
>> You are right. If I use the string parser it parses correctly. If I use the file parser it does not.
>> I need to check this out.
>
> And I found it. Thanks. — Mtt
>
> @@ -244,8 +244,8 @@
> ((#\v) (cons #\vtab cl))
> ((#\x) (cons (integer->char (read-hex ch)) cl))
> (else
> - (if (char-numeric? ch)
> - (cons (integer->char (read-oct ch)) cl)
> + (if (char-numeric? c1)
> + (cons (integer->char (read-oct c1)) cl)
> (cons c1 cl))))
> (read-char))))
> ((eq? ch #\") (cons '$string (lxlsr cl)))
Oh, nice and honest bug :-)
Thanks! Applied locally; switched to 0.80.4+ patches now which gives
good tcc progress.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2017-08-04 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 23:47 [ANN] nyacc 0.80.4 released Matt Wette
2017-08-01 20:53 ` Jan Nieuwenhuizen
2017-08-01 23:10 ` Matt Wette
2017-08-02 5:23 ` Jan Nieuwenhuizen
2017-08-02 12:13 ` Matt Wette
2017-08-02 12:22 ` Matt Wette
2017-08-04 10:31 ` Jan Nieuwenhuizen [this message]
2017-08-04 17:38 ` Matt Wette
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=8760e3fwuq.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guile-user@gnu.org \
--cc=matt.wette@gmail.com \
/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).