[src/trunk]: src/usr.bin/make/unit-tests make(1): fix comment in test about n...

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

details:   https://anonhg.NetBSD.org/src/rev/75adf4db1c6c
branches:  trunk
changeset: 948245:75adf4db1c6c
user:      rillig <rillig%NetBSD.org@localhost>
date:      Tue Dec 22 08:57:23 2020 +0000

description:
make(1): fix comment in test about null bytes in makefiles

diffstat:

 usr.bin/make/unit-tests/opt-file.mk |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (22 lines):

diff -r 83ac89847255 -r 75adf4db1c6c usr.bin/make/unit-tests/opt-file.mk
--- a/usr.bin/make/unit-tests/opt-file.mk       Tue Dec 22 08:51:30 2020 +0000
+++ b/usr.bin/make/unit-tests/opt-file.mk       Tue Dec 22 08:57:23 2020 +0000
@@ -1,4 +1,4 @@
-# $NetBSD: opt-file.mk,v 1.10 2020/12/22 08:51:30 rillig Exp $
+# $NetBSD: opt-file.mk,v 1.11 2020/12/22 08:57:23 rillig Exp $
 #
 # Tests for the -f command line option.
 
@@ -54,9 +54,9 @@
        @${MAKE} -r -f opt-file-trailing-whitespace -V VAR
        @rm opt-file-trailing-whitespace
 
-# If a file contains null bytes, the rest of the line is skipped, and parsing
-# continues in the next line.  Throughout the history of make, the behavior
-# has changed several times, sometimes knowingly, sometimes by accident.
+# If a makefile contains null bytes, it is an error.  Throughout the history
+# of make, the behavior has changed several times, sometimes intentionally,
+# sometimes by accident.
 #
 #      echo 'VAR=value' | tr 'l' '\0' > zero-byte.in
 #      printf '%s\n' 'all:' ': VAR=${VAR:Q}' >> zero-byte.in