History log of /src/tests/usr.bin/xlint/lint1/msg_230.c |
Revision | | Date | Author | Comments |
1.14 |
| 07-Jul-2023 |
rillig | lint: warn about function definitions without header declaration
The existing warning was only issued for function declarations, not for function definitions.
The interesting change in the tests is in msg_351.c. Many other tests use non-static functions due to their syntactic brevity. In these tests, the warning is disabled individually, to allow new functions to be added without generating warning 351.
|
1.13 |
| 24-Jun-2023 |
rillig | lint: don't warn about comparison between char and character constant
|
1.12 |
| 22-Feb-2023 |
rillig | lint: fix confusing message about nonportable character constants
|
1.11 |
| 26-Feb-2022 |
rillig | tests/lint: sync tests for platform-dependent character comparisons
|
1.10 |
| 09-Oct-2021 |
rillig | tests/lint: demonstrate wrong warning about nonportable char comparison
Seen in bin/sh/expand.c:273.
|
1.9 |
| 09-Oct-2021 |
rillig | lint: add more details to warning about nonportable character comparison
Especially when macros are involved, this makes it easier to see that there is a real problem.
Seen in bin/sh/expand.c:273, where a plain char is compared to numbers larger than 127.
|
1.8 |
| 28-Aug-2021 |
rillig | tests/lint: align tests for unsigned char and signed char
|
1.7 |
| 28-Aug-2021 |
rillig | tests/lint: extend test for nonportable character comparison
|
1.6 |
| 23-Aug-2021 |
rillig | tests/lint: add tests for integer comparisons
|
1.5 |
| 21-Aug-2021 |
rillig | tests/lint: guard against typos in test environment configuration
Some tests had "lint1-only-if" without a trailing colon, others included the trailing colon. The tests that included the trailing colon were run even though they were supposed to be skipped, and they failed, as could be expected.
To prevent further typos, always require the trailing colon, just as in "lint1-flags" and fail fast on unknown "lint1" comments.
|
1.4 |
| 03-Jul-2021 |
rillig | tests/lint: fix test for character comparison on macppc
On macppc, char == unsigned char, which generates one more warning than on platforms where char == signed char.
|
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 |
| 03-Jan-2021 |
rillig | lint: add tests for some of the messages
|
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.
|