The NetBSD Project

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

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

Request diff between arbitrary revisions

Default branch: MAIN

Revision 1.5 / (download) - annotate - [select for diffs], Tue Mar 28 14:44:35 2023 UTC (11 months, 1 week ago) by rillig
Branch: MAIN
CVS Tags: triaxx-drm, HEAD
Changes since 1.4: +3 -1 lines
Diff to previous 1.4 (colored)

lint: warn about extern declarations outside headers

Revision 1.4 / (download) - annotate - [select for diffs], Sat Jan 21 17:48:29 2023 UTC (13 months, 1 week ago) by rillig
Branch: MAIN
Changes since 1.3: +8 -4 lines
Diff to previous 1.3 (colored)

lint: add test for floating constant overflow

Revision 1.3 / (download) - annotate - [select for diffs], Thu Jun 16 21:24:41 2022 UTC (20 months, 2 weeks ago) by rillig
Branch: MAIN
CVS Tags: netbsd-10-base, netbsd-10-0-RC5, netbsd-10-0-RC4, netbsd-10-0-RC3, netbsd-10-0-RC2, netbsd-10-0-RC1, netbsd-10
Changes since 1.2: +3 -2 lines
Diff to previous 1.2 (colored)

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

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, 2 months 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  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 <>