CVS log for src/usr.bin/make/unit-tests/varmod-subst-regex.mk

Up to [cvs.NetBSD.org] / src / usr.bin / make / unit-tests

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

make: don't run erroneous commands in compat mode

When there is a parse or evaluation error in an expression that becomes
part of the command, don't run that command, as the result of the failed
evaluation typically contains garbage characters. Skip the remaining
commands from that target as well, as they may depend on the erroneous
command.

tests/make: fix typo in test for ':C' modifier

The expression ${U:...} was always undefined, as there was no variable
named 'U'; the intended form was ${:U:...}.  Due to this typo, the
comments in the tests for the ':S' and the ':C' modifier contradicted
each other.

tests/make: extend tests for include guards and empty expressions

make: fix crash in ':C' modifier on an empty expression

Since var.c 1.982 from 2021-12-13.

tests/make: replace 'variable expression' with 'expression'

Each expression is based on a variable, there's no need for the
verbosity.  The wording in make's diagnostics will be changed in a
follow-up commit.

tests/make: move and extend test for unmatched '\1' in ':C'

This test lived together with a few unrelated tests in moderrs.mk, it is
better placed in varmod-subst-regex.mk though.

While here, extend, document and explain the test since its purpose was
not obvious from reading the code alone.

make(1): add test for unknown modifier in :C modifier replacement

make(1): add tests for edge cases in the :C variable modifier

make(1): indent directives like .info, .if, .for consistently

Done by "pkglint -F *.mk", no manual corrections.

make(1): fix manual page about the modifiers of the :C modifier

make(1): move tests for :S, :C, :@ from modmisc to their separate tests

make(1): add dummies for fine-grained tests, one per single feature

The test names have been derived from the current manual page.

All these tests are dummies right now, and the code from the existing
tests will be moved into the new tests step by step.

This is done to prevent modmisc, escape, varmod-edge and varmisc from
growing without any bounds, and to reduce the side-effects of one test
to the others.