| History log of /src/tests/usr.bin/xlint/lint1/msg_230_uchar.c |
| Revision | | Date | Author | Comments |
| 1.13 |
| 08-Jul-2023 |
rillig | tests/lint: fix a few ilp32 tests
|
| 1.12 |
| 24-Jun-2023 |
rillig | lint: don't warn about comparison between char and character constant
|
| 1.11 |
| 27-Feb-2023 |
rillig | tests/lint: sync test for nonportable character comparisons
Message 230 was changed on 2023-02-22 but only tested on signed char
platforms.
|
| 1.10 |
| 22-Feb-2023 |
rillig | lint: fix confusing message about nonportable character constants
|
| 1.9 |
| 22-Jun-2022 |
rillig | 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.
|
| 1.8 |
| 14-Mar-2022 |
rillig | tests/lint: fix test about "non-portable character constant" on uchar
The warning is wrong, and it has been for a long time. For now just fix
the test to match the actual output. Seen on evbarm, which is one of
the platforms where a plain char is unsigned.
Noticed by Martin.
|
| 1.7 |
| 26-Feb-2022 |
rillig | tests/lint: sync tests for platform-dependent character comparisons
|
| 1.6 |
| 16-Dec-2021 |
rillig | tests/lint: ensure that tests on a message mention this message
|
| 1.5 |
| 16-Dec-2021 |
rillig | tests/lint: fix test on platforms where char is unsigned
In tree.c 1.385 from 2021-10-09, the format of the message changed. The
test for platforms where char is unsigned was not updated in that commit
because I had forgotten about it, and because lint1/check-msgs.lua only
checks the message in tests named exacty msg_000.c, but not msg_000_*.c.
Found by martin@.
|
| 1.4 |
| 28-Aug-2021 |
rillig | tests/lint: align tests for unsigned char and signed char
|
| 1.3 |
| 28-Aug-2021 |
rillig | tests/lint: extend test for nonportable character comparison
|
| 1.2 |
| 21-Aug-2021 |
rillig | tests/lint: guard against typos in test environment configuration
Some tests had "lint1-only-if" without a trailing colon, others included
the trailing colon. The tests that included the trailing colon were run
even though they were supposed to be skipped, and they failed, as could
be expected.
To prevent further typos, always require the trailing colon, just as in
"lint1-flags" and fail fast on unknown "lint1" comments.
|
| 1.1 |
| 03-Jul-2021 |
rillig | tests/lint: fix test for character comparison on macppc
On macppc, char == unsigned char, which generates one more warning than
on platforms where char == signed char.
|
