| History log of /src/tests/usr.bin/xlint/lint1/msg_129.c |
| Revision | | Date | Author | Comments |
| 1.11 |
| 17-Sep-2025 |
rillig | lint: answer two questions from the code by writing tests for them
|
| 1.10 |
| 29-Oct-2024 |
rillig | lint: fix warning about null effect in GCC statement expressions
|
| 1.9 |
| 29-Oct-2024 |
rillig | tests/lint: demonstrate wrong warning about 'null effect'
Seen in sys/timevar.h:250 and other places.
|
| 1.8 |
| 02-Aug-2023 |
rillig | branches: 1.8.2;
lint: distinguish between arguments and parameters
|
| 1.7 |
| 28-Mar-2023 |
rillig | lint: warn about extern declarations outside headers
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
|
| 1.6 |
| 16-Jun-2022 |
rillig | tests/lint: make expectation lines in the tests more detailed
This commit migrates msg_100 until msg_199.
|
| 1.5 |
| 21-Aug-2021 |
rillig | lint: do not warn about '(void)arg' and similar expressions
In the current NetBSD build, 5260 of the 46264 total lint warnings are
about expressions that have a null effect. Most of these occurrences
follow well-established patterns, which makes the warnings bogus.
Remove these warnings.
|
| 1.4 |
| 21-Aug-2021 |
rillig | tests/lint: demonstrate wrong warnings for 'null effect' expressions
|
| 1.3 |
| 30-Jan-2021 |
rillig | lint: fix wrong 'expression has null effect'
|
| 1.2 |
| 30-Jan-2021 |
rillig | lint: add test for 129, possibly demonstrating a bug in lint
|
| 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.
|
| 1.8.2.1 |
| 02-Aug-2025 |
perseant | Sync with HEAD
|
