|
Revision tags: perseant-exfatfs-base-20250801 netbsd-11-base
|
|
| #
1.9 |
|
12-Apr-2025 |
rillig |
lint: s/illegal/invalid/g
Lint does not provide legal advice.
|
|
Revision tags: perseant-exfatfs-base-20240630 perseant-exfatfs-base
|
|
| #
1.8 |
|
28-Mar-2023 |
rillig |
branches: 1.8.2;
lint: warn about extern declarations outside headers
https://mail-index.netbsd.org/tech-userlevel/2023/03/15/msg013727.html
|
|
Revision tags: netbsd-10-1-RELEASE netbsd-10-0-RELEASE netbsd-10-0-RC6 netbsd-10-0-RC5 netbsd-10-0-RC4 netbsd-10-0-RC3 netbsd-10-0-RC2 netbsd-10-0-RC1 netbsd-10-base
|
|
| #
1.7 |
|
17-Jun-2022 |
rillig |
tests/lint: add more details to tests from msg_300 until msg_343
|
|
Revision tags: cjep_sun2x-base1 cjep_sun2x-base cjep_staticlib_x-base1 cjep_staticlib_x-base
|
|
| #
1.6 |
|
05-Apr-2021 |
rillig |
tests/lint: one comment per expected diagnostic
This makes it possible to check for diagnostics that contain commas.
|
| #
1.5 |
|
28-Feb-2021 |
rillig |
tests/lint: keep messages in test files in sync with actual messages
Each of the tests named msg_*.c repeats the template of the message, to
make the test somewhat self-contained when viewed in isolation.
This creates a redundancy, and keeping track of this manually is next to
impossible. I tried it and failed in 9 cases, even though it has just
been 2 months since I myself created the initial files and I knew all
the time that this redundancy exists.
Be fool-proof for the future by checking this automatically.
|
| #
1.4 |
|
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.3 |
|
02-Jan-2021 |
rillig |
lint: fix message 308 "Invalid type for _Complex"
Previously, lint aborted since it didn't expect tspec_name to be called
with NOTSPEC, which at that point was the only possible value of
dcs->d_cmod.
|
| #
1.2 |
|
02-Jan-2021 |
rillig |
lint: add test for message 308 "Invalid type %s for _Complex"
|
| #
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.
|