| History log of /src/tests/usr.bin/xlint/lint1/msg_160.c |
| Revision | | Date | Author | Comments |
| 1.10 |
| 28-Mar-2023 |
rillig | lint: warn about extern declarations outside headers
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
|
| 1.9 |
| 16-Jun-2022 |
rillig | tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
| 1.8 |
| 18-May-2022 |
rillig | lint: do not warn about '==' on the right-hand side of ','
|
| 1.7 |
| 18-May-2022 |
rillig | tests/lint: add more examples for warning in comma expression
|
| 1.6 |
| 09-Oct-2021 |
rillig | tests/lint: add examples for bogus warning 160 and for error 323
|
| 1.5 |
| 31-Jan-2021 |
rillig | lint: fix strange message about nested '==' operators
If one of the nested subexpressions is parenthesized, the author
probably knew how these expressions are evaluated. Therefore don't warn
in such a situation.
Maybe the original author once made a typo and tried to initialize
variables but instead compared them, like this:
int a, b, c;
a == b == c;
This would explain the text of the message, which still sounds strange.
At least it doesn't show up as often anymore.
|
| 1.4 |
| 31-Jan-2021 |
rillig | lint: add more test cases for strange '==' warning 160
|
| 1.3 |
| 31-Jan-2021 |
rillig | lint: add expections to tests
msg_098: fix suffix for floating point constant
msg_127: remove prototype
msg_146: fix return type
|
| 1.2 |
| 09-Jan-2021 |
rillig | lint: add test for message 160
|
| 1.1 |
| 02-Jan-2021 |
rillig | lint: add a test for each message produced by lint1
Having a test for each message ensures that upcoming refactorings don't
break the basic functionality. Adding the tests will also discover
previously unknown bugs in lint.
The tests ensure that every lint message can actually be triggered, and
they demonstrate how to do so. Having a separate file for each test
leaves enough space for documenting historical anecdotes, rationale or
edge cases, keeping them away from the source code.
The interesting details of this commit are in Makefile and
t_integration.sh. All other files are just auto-generated.
When running the tests as part of ATF, they are packed together as a
single test case. Conceptually, it would have been better to have each
test as a separate test case, but ATF quickly becomes very slow as soon
as a test program defines too many test cases, and 50 is already too
many. The time complexity is O(n^2), not O(n) as one would expect.
It's the same problem as in tests/usr.bin/make, which has over 300 test
cases as well.
|
