Module Name: src
Committed By: rillig
Date: Sun Feb 5 13:06:36 UTC 2023
Modified Files:
src/usr.bin/xlint/lint1: README.md
Log Message:
tests/lint: update instructions for adding a new test
The redundant variable 'FILES' no longer needs up be updated.
To generate a diff of this commit:
cvs rdiff -u -r1.10 -r1.11 src/usr.bin/xlint/lint1/README.md
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/usr.bin/xlint/lint1/README.md
diff -u src/usr.bin/xlint/lint1/README.md:1.10 src/usr.bin/xlint/lint1/README.md:1.11
--- src/usr.bin/xlint/lint1/README.md:1.10 Sat Jan 21 21:14:38 2023
+++ src/usr.bin/xlint/lint1/README.md Sun Feb 5 13:06:36 2023
@@ -1,4 +1,4 @@
-[//]: # ($NetBSD: README.md,v 1.10 2023/01/21 21:14:38 rillig Exp $)
+[//]: # ($NetBSD: README.md,v 1.11 2023/02/05 13:06:36 rillig Exp $)
# Introduction
@@ -224,7 +224,7 @@ They do this by placing `expect` comment
The comment `/* expect+1: ... */` expects a diagnostic to be generated for the
code 1 line below, `/* expect-5: ... */` expects a diagnostic to be generated
for the code 5 lines above.
-Each `expect` comment must be in a single line.
+An `expect` comment cannot span multiple lines.
At the start and the end of the comment, the placeholder `...` stands for an
arbitrary sequence of characters.
There may be other code or comments in the same line of the `.c` file.
@@ -237,8 +237,7 @@ Most other tests focus on a single featu
1. Run `make add-test NAME=test_name`.
2. Run `cd ../../../tests/usr.bin/xlint/lint1`.
-3. Sort the `FILES` lines in `Makefile`.
-4. Make the test generate the desired diagnostics.
-5. Run `./accept.sh test_name` until it no longer complains.
-6. Run `cd ../../..`.
-7. Run `cvs commit distrib/sets/lists/tests/mi tests/usr.bin/xlint`.
+3. Make the test generate the desired diagnostics.
+4. Run `./accept.sh test_name` until it no longer complains.
+5. Run `cd ../../..`.
+6. Run `cvs commit distrib/sets/lists/tests/mi tests/usr.bin/xlint`.
