The NetBSD Project

CVS log for src/tests/usr.bin/xlint/lint1/msg_003.c

[BACK] Up to [cvs.NetBSD.org] / src / tests / usr.bin / xlint / lint1

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.7 / (download) - annotate - [select for diffs], Wed Aug 2 18:51:25 2023 UTC (6 months, 3 weeks ago) by rillig
Branch: MAIN
CVS Tags: HEAD
Changes since 1.6: +8 -8 lines
Diff to previous 1.6 (colored)

lint: distinguish between arguments and parameters

Revision 1.6 / (download) - annotate - [select for diffs], Fri Jul 7 19:45:22 2023 UTC (7 months, 3 weeks ago) by rillig
Branch: MAIN
Changes since 1.5: +3 -1 lines
Diff to previous 1.5 (colored)

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.

Revision 1.5 / (download) - annotate - [select for diffs], Wed Jun 15 20:18:31 2022 UTC (20 months, 1 week ago) by rillig
Branch: MAIN
CVS Tags: netbsd-10-base, netbsd-10-0-RC4, netbsd-10-0-RC3, netbsd-10-0-RC2, netbsd-10-0-RC1, netbsd-10
Changes since 1.4: +7 -4 lines
Diff to previous 1.4 (colored)

tests/lint: replace 'expect' comments with 'expect+-' comments

The 'expect+-' comments provide more context, which makes it easier to
read the .c files on their own, without having to look up the actual
diagnostics in the .exp files.

Add tests for messages 105 and 106, which were about the obscure feature
of some traditional C compilers that allowed the expression 'x->member'
to access a struct member, even if 'x' had integer type.

The remaining tests will be migrated in a future commit.

Revision 1.4 / (download) - annotate - [select for diffs], Sun Feb 28 12:40:00 2021 UTC (2 years, 11 months ago) by rillig
Branch: MAIN
CVS Tags: cjep_sun2x-base1, cjep_sun2x-base, cjep_sun2x, cjep_staticlib_x-base1, cjep_staticlib_x-base, cjep_staticlib_x
Changes since 1.3: +2 -2 lines
Diff to previous 1.3 (colored)

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.

Revision 1.3 / (download) - annotate - [select for diffs], Sun Jan 31 11:12:07 2021 UTC (3 years ago) by rillig
Branch: MAIN
Changes since 1.2: +4 -4 lines
Diff to previous 1.2 (colored)

lint: add expections to tests

msg_098: fix suffix for floating point constant
msg_127: remove prototype
msg_146: fix return type

Revision 1.2 / (download) - annotate - [select for diffs], Sun Jan 31 09:21:24 2021 UTC (3 years ago) by rillig
Branch: MAIN
Changes since 1.1: +9 -3 lines
Diff to previous 1.1 (colored)

lint: add a few more tests

Revision 1.1 / (download) - annotate - [select for diffs], Sat Jan 2 10:22:42 2021 UTC (3 years, 1 month ago) by rillig
Branch: MAIN

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.

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.




CVSweb <webmaster@jp.NetBSD.org>