CVS log for src/tests/usr.bin/xlint/lint1/msg_062.c
![[BACK]](/icons/back.gif)
Up to [cvs.NetBSD.org] / src / tests / usr.bin / xlint / lint1
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Revision 1.9: download - view: text, markup, annotated - select for diffs
Fri Jan 3 03:14:47 2025 UTC (2 months, 2 weeks ago) by rillig
Branches: MAIN
CVS tags: HEAD
Diff to: previous 1.8: preferred, colored
Changes since revision 1.8: +2 -2
lines
lint: add detail to message about obsolete identifier list
Revision 1.8: download - view: text, markup, annotated - select for diffs
Sun Dec 1 18:37:54 2024 UTC (3 months, 2 weeks ago) by rillig
Branches: MAIN
Diff to: previous 1.7: preferred, colored
Changes since revision 1.7: +2 -1
lines
lint: warn about function definitions that still use identifier lists
Revision 1.7: download - view: text, markup, annotated - select for diffs
Fri Jul 7 19:45:22 2023 UTC (20 months, 2 weeks ago) by rillig
Branches: MAIN
CVS tags: perseant-exfatfs-base-20240630,
perseant-exfatfs-base,
perseant-exfatfs
Diff to: previous 1.6: preferred, colored
Changes since revision 1.6: +3 -1
lines
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 - view: text, markup, annotated - select for diffs
Sat Oct 1 09:42:40 2022 UTC (2 years, 5 months ago) by rillig
Branches: MAIN
CVS tags: netbsd-10-base,
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
Diff to: previous 1.5: preferred, colored
Changes since revision 1.5: +2 -2
lines
lint: add hyphen to adjective 'old-style'
Revision 1.5: download - view: text, markup, annotated - select for diffs
Tue Jun 21 21:18:30 2022 UTC (2 years, 9 months ago) by rillig
Branches: MAIN
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +2 -2
lines
lint: add quotes and details to some more messages
Revision 1.4: download - view: text, markup, annotated - select for diffs
Sun Apr 24 20:08:23 2022 UTC (2 years, 10 months ago) by rillig
Branches: MAIN
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +2 -1
lines
lint: error out on declarations with implicit int type
Revision 1.3: download - view: text, markup, annotated - select for diffs
Sun Feb 27 20:02:44 2022 UTC (3 years ago) by rillig
Branches: MAIN
Diff to: previous 1.2: preferred, colored
Changes since revision 1.2: +6 -3
lines
tests/lint: add tests for messages about old-style functions
Revision 1.2: download - view: text, markup, annotated - select for diffs
Sun Feb 21 09:07:58 2021 UTC (4 years, 1 month ago) by rillig
Branches: MAIN
CVS tags: cjep_sun2x-base1,
cjep_sun2x-base,
cjep_sun2x,
cjep_staticlib_x-base1,
cjep_staticlib_x-base,
cjep_staticlib_x
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +2 -2
lines
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 - view: text, markup, annotated - select for diffs
Sat Jan 2 10:22:43 2021 UTC (4 years, 2 months ago) by rillig
Branches: 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.
CVSweb <webmaster@jp.NetBSD.org>