From: "Jan (janneke) Nieuwenhuizen" <janneke@gnu.org>
To: 41716@debbugs.gnu.org
Subject: bug#41716: [PATCH] reader: Use invalid rather than illegal.
Date: Thu, 4 Jun 2020 21:26:23 +0200 [thread overview]
Message-ID: <20200604192623.10350-1-janneke@gnu.org> (raw)
* libguile/read.c (scm_read_string_like_syntax): All characters are
permitted by law; some aren't valid in certain contexts.
---
libguile/read.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libguile/read.c b/libguile/read.c
index 040a178348..122a643018 100644
--- a/libguile/read.c
+++ b/libguile/read.c
@@ -704,7 +704,7 @@ scm_read_string_like_syntax (int chr, SCM port, scm_t_read_opts *opts)
break;
bad_escaped:
scm_i_input_error (FUNC_NAME, port,
- "illegal character in escape sequence: ~S",
+ "invalid character in escape sequence: ~S",
scm_list_1 (SCM_MAKE_CHAR (c)));
}
}
--
2.26.2
next reply other threads:[~2020-06-04 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 19:26 Jan (janneke) Nieuwenhuizen [this message]
2020-06-17 21:27 ` bug#41716: [PATCH] reader: Use invalid rather than illegal Ludovic Courtès
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=20200604192623.10350-1-janneke@gnu.org \
--to=janneke@gnu.org \
--cc=41716@debbugs.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).