From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-user@gnu.org
Subject: Nyacc bad escape sequence compiling tcc.h: is_space
Date: Sat, 03 Jun 2017 09:10:55 +0200 [thread overview]
Message-ID: <87k24tczr4.fsf@gnu.org> (raw)
In-Reply-To: <ACB305B7-8540-49C0-83E0-3B8832BE9C06@gmail.com> (Matt Wette's message of "Fri, 26 May 2017 21:23:33 -0700")
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
Matt Wette writes:
Hi Matt!
The second tcc.c problem looks like a silly little bug?
Backtrace:
19 (apply-smob/1 #<catch-closure db0080>)
In ice-9/boot-9.scm:
713:2 18 (call-with-prompt _ _ #<procedure default-prompt-handler (k proc)>)
In ice-9/eval.scm:
619:8 17 (_ #(#(#<directory (guile-user) e61140>)))
619:8 16 (_ #(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#<directory (mescc) e…>) …) …) …) …) …) …) …) …) …) …) …) …) …) …))
In ice-9/ports.scm:
462:17 15 (call-with-output-file _ _ #:binary _ #:encoding _)
473:4 14 (with-output-to-port _ _)
In ice-9/eval.scm:
293:34 13 (_ #(#(#<directory (mescc) e87aa0> () () ("bugs/is-space.c") #f #f () ())))
In srfi/srfi-1.scm:
592:17 12 (map1 ("bugs/is-space.c"))
In ice-9/ports.scm:
444:17 11 (call-with-input-file _ _ #:binary _ #:encoding _ #:guess-encoding _)
469:4 10 (with-input-from-port _ _)
In /tmp/guix-build-mes-git.drv-0/source/module/language/c99/compiler.mes:
2194:16 9 (_)
99:21 8 (c99-input->ast #:defines _ #:includes _)
In ice-9/boot-9.scm:
837:9 7 (catch c99-error #<procedure 101b500 at nyacc/lang/c99/parser.scm:78:3 ()> #<procedure 7f1929b30…> …)
In nyacc/lang/c99/parser.scm:
85:13 6 (_)
In ice-9/boot-9.scm:
837:9 5 (catch nyacc-error #<procedure 1043f60 at nyacc/lang/c99/parser.scm:42:7 ()> #<procedure 7f1929b…> …)
In nyacc/parse.scm:
104:35 4 (_ #<procedure 1017c00 at nyacc/lang/c99/body.scm:304:8 ()> #:debug _)
In nyacc/lang/c99/body.scm:
537:21 3 (_)
519:16 2 (read-token)
In nyacc/lex.scm:
274:28 1 (read-c-chlit _)
In unknown file:
0 (scm-error misc-error #f "~A" ("bad escape sequence") #f)
ERROR: In procedure scm-error:
ERROR: bad escape sequence
[-- Attachment #2: is-space.c --]
[-- Type: application/octet-stream, Size: 237 bytes --]
static inline int is_space(int ch) {
#if !__MESC__
// cannot enable this...
return ch == ' ' || ch == '\t' || ch == '\v' || ch == '\f' || ch == '\r';
return ch == ' ' || ch == '\t';
#else
return ch == ' ' || ch == '\t';
#endif
}
[-- Attachment #3: Type: text/plain, Size: 152 bytes --]
--
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-06-03 7:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 4:23 [ANN] NYACC version 0.79.4 is released Matt Wette
2017-05-29 15:42 ` Matt Wette
2017-05-29 15:54 ` Nala Ginrut
2017-05-29 16:06 ` Matt Wette
2017-05-29 16:08 ` Matt Wette
2017-05-29 16:14 ` Nala Ginrut
2017-06-03 7:03 ` Nyacc parse error tcc.h: DEF_BWL Jan Nieuwenhuizen
2017-06-03 12:59 ` Matt Wette
2017-06-03 13:03 ` Matt Wette
2017-06-03 19:08 ` Jan Nieuwenhuizen
2017-06-03 7:10 ` Jan Nieuwenhuizen [this message]
2017-06-03 7:18 ` Nyacc parse error tcc.h: anonymous union in struct Jan Nieuwenhuizen
2017-06-03 15:19 ` 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=87k24tczr4.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).