| History log of /src/tests/usr.bin/xlint/lint1/msg_220.c |
| Revision | | Date | Author | Comments |
| 1.11 |
| 08-May-2025 |
rillig | lint: fix merging type attributes
|
| 1.10 |
| 08-May-2025 |
rillig | tests/lint: demonstrate ignored function attributes
|
| 1.9 |
| 28-Mar-2023 |
rillig | branches: 1.9.2;
lint: warn about extern declarations outside headers
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
|
| 1.8 |
| 16-Jun-2022 |
rillig | tests/lint: add more details to messages in msg_200 until msg_299
Add some tests that were previously empty. Some other tests are still
empty.
|
| 1.7 |
| 29-Aug-2021 |
rillig | lint: allow 'fallthrough' as alternative spelling of FALLTHROUGH
Seen in unbound/lookup3.c.
No change to the documentation since the canonical spelling is still the
same.
|
| 1.6 |
| 29-Aug-2021 |
rillig | tests/lint: test lowercase fallthrough
|
| 1.5 |
| 29-Aug-2021 |
rillig | lint: accept keyword variant FALL THROUGH as alias to FALLTHROUGH
Seen in archive_string.c, macro WRITE_UC.
No documentation change since the canonical spelling of this keyword
stays the same.
|
| 1.4 |
| 29-Aug-2021 |
rillig | tests/lint: test variants of the FALLTHROUGH comment
|
| 1.3 |
| 12-Apr-2021 |
christos | Add an example of attribute fallthrough
|
| 1.2 |
| 30-Jan-2021 |
rillig | lint: add tests that trigger a few more 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.
|
| 1.9.2.1 |
| 02-Aug-2025 |
perseant | Sync with HEAD
|
