[src/trunk]: src/tests/usr.bin/xlint/lint1 tests/lint: fix comment about back...

[rillig <rillig%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/11cc9fac7632
branches:  trunk
changeset: 364633:11cc9fac7632
user:      rillig <rillig%NetBSD.org@localhost>
date:      Fri Apr 01 21:12:42 2022 +0000

description:
tests/lint: fix comment about backslash-newline

diffstat:

 tests/usr.bin/xlint/lint1/lex_char.c |  8 +++++---
 1 files changed, 5 insertions(+), 3 deletions(-)

diffs (22 lines):

diff -r 4ece65d6403d -r 11cc9fac7632 tests/usr.bin/xlint/lint1/lex_char.c
--- a/tests/usr.bin/xlint/lint1/lex_char.c      Fri Apr 01 21:09:24 2022 +0000
+++ b/tests/usr.bin/xlint/lint1/lex_char.c      Fri Apr 01 21:12:42 2022 +0000
@@ -1,4 +1,4 @@
-/*     $NetBSD: lex_char.c,v 1.4 2021/06/29 07:28:01 rillig Exp $      */
+/*     $NetBSD: lex_char.c,v 1.5 2022/04/01 21:12:42 rillig Exp $      */
 # 3 "lex_char.c"
 
 /*
@@ -60,8 +60,10 @@
 }
 
 /*
- * Even though backslash-newline is not supported by C99, lint accepts it
- * in any mode, even for traditional C.
+ * The sequence backslash-newline is handled in an early stage of
+ * translation (C90 5.1.1.2 item 2, C99 5.1.1.2 item 2, C11 5.1.1.2 item 2),
+ * which allows it in character literals as well.  This doesn't typically
+ * occur in practice though.
  */
 char ch = '\
 \