From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: Guile User Mailing List <guile-user@gnu.org>
Subject: Re: fix for c99dev string escape char read
Date: Thu, 23 Nov 2017 08:02:01 +0100 [thread overview]
Message-ID: <874lplh40m.fsf@gnu.org> (raw)
In-Reply-To: <878texh7na.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Thu, 23 Nov 2017 06:43:37 +0100")
Jan Nieuwenhuizen writes:
> For now I'm happy; we'll see.
Still happy, found a bug though; on c99dev plus my previous patch this happens
--8<---------------cut here---------------start------------->8---
(use-modules (nyacc lang c99 parser) (ice-9 pretty-print))
(pretty-print (with-input-from-string "#define ELF \"\\177ELF\"\nchar *a = ELF;" parse-c99))
=>
(trans-unit
(decl (decl-spec-list (type-spec (fixed-type "char")))
(init-declr-list
(init-declr
(ptr-declr (pointer) (ident "a"))
(initzer (p-expr (string "177ELF")))))))
--8<---------------cut here---------------end--------------->8---
master (correctly) gives
... (p-expr (string "\x7fELF"))
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-11-23 7:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 17:19 [ANN] nyacc 0.82.2 is released Matt Wette
2017-11-11 18:37 ` [ANN] nyacc 0.82.3 " Matt Wette
2017-11-11 19:53 ` Jan Nieuwenhuizen
2017-11-11 19:59 ` Jan Nieuwenhuizen
2017-11-11 20:00 ` Matt Wette
2017-11-11 22:03 ` [ANN] nyacc 0.82.4 " Matt Wette
2017-11-23 2:11 ` fix for c99dev string escape char read Jan Nieuwenhuizen
2017-11-23 3:28 ` Matt Wette
2017-11-23 5:43 ` Jan Nieuwenhuizen
2017-11-23 7:02 ` Jan Nieuwenhuizen [this message]
2017-11-23 14:45 ` Matt Wette
2017-11-23 15:04 ` Matt Wette
2017-11-23 15:14 ` 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=874lplh40m.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).