OpenGrok
Cross Reference: msg_101.c
xref
: /
src
/
tests
/
usr.bin
/
xlint
/
lint1
/
msg_101.c
Home
|
History
|
Annotate
|
Download
|
only in
lint1
History log of
/src/tests/usr.bin/xlint/lint1/msg_101.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
04-Jul-2021
rillig
lint: replace wrong assumption with citation from C99
No functional change.
1.8
04-Jul-2021
rillig
lint: document where to fix missing const in lvalue-to-rvalue
No functional change.
1.7
04-Jul-2021
rillig
lint: align messages for invalid left operand of '.' or '->'
1.6
30-Jun-2021
rillig
lint: fix type name in message 101 for wrong member name
1.5
30-Jun-2021
rillig
tests/lint: extend tests for message 101
This demonstrates the wrong type name in the message.
1.4
30-Mar-2021
rillig
lint: add type information for message about unknown member name
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
08-Jan-2021
rillig
lint: add tests for several 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.
Indexes created Wed Oct 15 16:09:53 GMT 2025