The NetBSD Project

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

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

Request diff between arbitrary revisions


Default branch: MAIN


Revision 1.9 / (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.8: +2 -2 lines
Diff to previous 1.8 (colored)

lint: distinguish between arguments and parameters

Revision 1.8 / (download) - annotate - [select for diffs], Sun Jul 9 11:18:55 2023 UTC (7 months, 2 weeks ago) by rillig
Branch: MAIN
Changes since 1.7: +2 -2 lines
Diff to previous 1.7 (colored)

lint: clean up wording in diagnostics

Use the term 'parameter' as defined in C99 3.15.

Revision 1.7 / (download) - annotate - [select for diffs], Fri Jul 7 19:45:22 2023 UTC (7 months, 2 weeks ago) by rillig
Branch: MAIN
Changes since 1.6: +3 -1 lines
Diff to previous 1.6 (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.6 / (download) - annotate - [select for diffs], Wed Jun 22 19:23:18 2022 UTC (20 months 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.5: +7 -7 lines
Diff to previous 1.5 (colored)

lint: add quotes around placeholders for the remaining messages

Reword some of the messages slightly, exchanging brevity for clarity.

Message 138 is kept as-is, as it is not yet covered by any tests.

Message 240 is kep as-is, as it is unreachable.

Revision 1.5 / (download) - annotate - [select for diffs], Sun Sep 5 19:16:37 2021 UTC (2 years, 5 months ago) by rillig
Branch: MAIN
Changes since 1.4: +25 -8 lines
Diff to previous 1.4 (colored)

tests/lint: document placement of lint comments

Revision 1.4 / (download) - annotate - [select for diffs], Sun Sep 5 18:39:58 2021 UTC (2 years, 5 months ago) by rillig
Branch: MAIN
Changes since 1.3: +1 -3 lines
Diff to previous 1.3 (colored)

tests/lint: clean up test for misplaced lint comments

A varargs comment that appears in the function body is already covered
by varargs_bad_body.  Cleaning up this test makes sure that the warning
is indeed triggered by the comment in the parameters declaration.

Revision 1.3 / (download) - annotate - [select for diffs], Mon Aug 30 19:48:21 2021 UTC (2 years, 5 months ago) by rillig
Branch: MAIN
Changes since 1.2: +56 -3 lines
Diff to previous 1.2 (colored)

tests/lint: test varargs, printflike, scanflike

Revision 1.2 / (download) - annotate - [select for diffs], Sun Feb 21 09:07:58 2021 UTC (3 years 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.1: +2 -2 lines
Diff to previous 1.1 (colored)

lint: force each test to declare the expected diagnostics

By listing the expected diagnostics directly at the code that triggers
the diagnostics, it is easier to cross-check whether the diagnostics
make sense.

No functional change to lint itself.

Revision 1.1 / (download) - annotate - [select for diffs], Sat Jan 2 10:22:44 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>