CVS log for src/tests/usr.bin/xlint/lint1/Attic/d_c99_complex_split.exp

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

Request diff between arbitrary revisions

Default branch: MAIN

Revision 1.4, Fri Jun 17 20:23:58 2022 UTC (22 months ago) by rillig
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +0 -0 lines
FILE REMOVED

tests/lint: remove .exp files, as they have become redundant

Now that each lint1 test lists all generated diagnostics as 'expect'
comments, the information from the .exp files is no longer needed.  The
only information that gets lost is the order of the diagnostics, which
is mostly relevant for paired messages like 'inconsistent definition' +
'previous definition was here'.

Revision 1.3 / (download) - annotate - [select for diffs], Sat Jan 15 14:22:03 2022 UTC (2 years, 3 months ago) by rillig
Branch: MAIN
Changes since 1.2: +1 -1 lines
Diff to previous 1.2 (colored)

tests/lint: expect complete messages in feature tests

Previously, the tests contained many comments like /* expect: 123 */,
which were useless to a casual reader since nobody is expected to learn
lint's message IDs by heart.  Replace these with the complete
diagnostics, to show what lint is complaining about.

The tests named msg_*.c have been left unmodified since they mention the
full message text in their header comment.

No functional change.

Revision 1.2 / (download) - annotate - [select for diffs], Fri Apr 9 21:42:12 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: +1 -3 lines
Diff to previous 1.1 (colored)

lint: fix wrong warning about uninitialized _Complex variable

Seen in divxc3.c.

Revision 1.1 / (download) - annotate - [select for diffs], Fri Apr 9 21:07:39 2021 UTC (3 years ago) by rillig
Branch: MAIN

tests/lint: demonstrate wrong lint warning about complex variables

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.