head	1.11;
access;
symbols
	netbsd-11-0-RC4:1.11
	netbsd-11-0-RC3:1.11
	netbsd-11-0-RC2:1.11
	netbsd-11-0-RC1:1.11
	perseant-exfatfs-base-20250801:1.11
	netbsd-11:1.11.0.2
	netbsd-11-base:1.11
	netbsd-10-1-RELEASE:1.5
	perseant-exfatfs-base-20240630:1.7
	perseant-exfatfs:1.7.0.2
	perseant-exfatfs-base:1.7
	netbsd-10-0-RELEASE:1.5
	netbsd-10-0-RC6:1.5
	netbsd-10-0-RC5:1.5
	netbsd-10-0-RC4:1.5
	netbsd-10-0-RC3:1.5
	netbsd-10-0-RC2:1.5
	netbsd-10-0-RC1:1.5
	netbsd-10:1.5.0.2
	netbsd-10-base:1.5
	cjep_sun2x-base1:1.4
	cjep_sun2x:1.4.0.4
	cjep_sun2x-base:1.4
	cjep_staticlib_x-base1:1.4
	cjep_staticlib_x:1.4.0.2
	cjep_staticlib_x-base:1.4;
locks; strict;
comment	@# @;


1.11
date	2025.06.28.22.39.28;	author rillig;	state Exp;
branches;
next	1.10;
commitid	CDDpACH2g2jV3I0G;

1.10
date	2025.03.30.09.51.50;	author rillig;	state Exp;
branches;
next	1.9;
commitid	veGmSzVhPiW2G4PF;

1.9
date	2024.08.06.18.00.17;	author rillig;	state Exp;
branches;
next	1.8;
commitid	1R0ZDok3menTZMkF;

1.8
date	2024.07.04.20.18.40;	author rillig;	state Exp;
branches;
next	1.7;
commitid	75IS4XOhTa8VOygF;

1.7
date	2023.06.01.20.56.35;	author rillig;	state Exp;
branches
	1.7.2.1;
next	1.6;
commitid	j3tIvMRlxolKQhrE;

1.6
date	2023.03.04.08.07.29;	author rillig;	state Exp;
branches;
next	1.5;
commitid	19sa4fPF6fo1tMfE;

1.5
date	2021.12.27.18.54.19;	author rillig;	state Exp;
branches;
next	1.4;
commitid	Moqa12wsG1tQVjmD;

1.4
date	2020.11.15.14.58.14;	author rillig;	state Exp;
branches;
next	1.3;
commitid	cic6f0a3jiRYHZvC;

1.3
date	2020.11.08.22.28.05;	author rillig;	state Exp;
branches;
next	1.2;
commitid	CUuXPABH7lXgq8vC;

1.2
date	2020.09.14.06.22.59;	author rillig;	state Exp;
branches;
next	1.1;
commitid	qX9DDiiyfJmNQYnC;

1.1
date	2020.08.16.12.07.51;	author rillig;	state Exp;
branches;
next	;
commitid	coEgPk3hgfeYGhkC;

1.7.2.1
date	2025.08.02.05.58.32;	author perseant;	state Exp;
branches;
next	;
commitid	23j6GFaDws3O875G;


desc
@@


1.11
log
@make: consistently use double quotes in error messages

Previously, some error messages used single quotes, very few used
backticks or parentheses, most already used double quotes.

While here, reword a few error messages to be clearer or more consistent
with related error messages.
@
text
@make: cond-token-number.mk:16: Malformed conditional "-0"
make: cond-token-number.mk:27: Malformed conditional "+0"
make: cond-token-number.mk:38: Malformed conditional "!-1"
make: cond-token-number.mk:49: Malformed conditional "!+1"
make: Fatal errors encountered -- cannot continue
make: stopped making "all" in unit-tests
exit status 1
@


1.10
log
@make: use '"filename" line 123' for locations instead of 'filename:123'

The format 'filename:123' is commonly used for identifying a location in
a file. Text editors recognize it and allow quick navigation through it.
The previous format was specific to make and would have required custom
support in editors.

The new format was already used in stack traces, except for the first
line. Now all lines use the same format.
@
text
@d1 4
a4 4
make: cond-token-number.mk:16: Malformed conditional '-0'
make: cond-token-number.mk:27: Malformed conditional '+0'
make: cond-token-number.mk:38: Malformed conditional '!-1'
make: cond-token-number.mk:49: Malformed conditional '!+1'
@


1.9
log
@make: in error message about conditionals, use single quotes

Single quotes are used less often in the conditionals themselves, which
leads to fewer confusions.
@
text
@d1 4
a4 4
make: "cond-token-number.mk" line 16: Malformed conditional '-0'
make: "cond-token-number.mk" line 27: Malformed conditional '+0'
make: "cond-token-number.mk" line 38: Malformed conditional '!-1'
make: "cond-token-number.mk" line 49: Malformed conditional '!+1'
@


1.8
log
@make: on error, print the targets to be made

This helps to understand situations with several nested sub-makes in
varying directories.
@
text
@d1 4
a4 4
make: "cond-token-number.mk" line 16: Malformed conditional (-0)
make: "cond-token-number.mk" line 27: Malformed conditional (+0)
make: "cond-token-number.mk" line 38: Malformed conditional (!-1)
make: "cond-token-number.mk" line 49: Malformed conditional (!+1)
@


1.7
log
@tests/make: force line-based diagnostics to be listed in the tests

This way, contradictions between the intended output and the actual
output are closer together and have a better chance of being spotted.
@
text
@d6 1
a6 1
make: stopped in unit-tests
@


1.7.2.1
log
@Sync with HEAD
@
text
@d1 4
a4 4
make: cond-token-number.mk:16: Malformed conditional "-0"
make: cond-token-number.mk:27: Malformed conditional "+0"
make: cond-token-number.mk:38: Malformed conditional "!-1"
make: cond-token-number.mk:49: Malformed conditional "!+1"
d6 1
a6 1
make: stopped making "all" in unit-tests
@


1.6
log
@tests/make: test very small and very large numbers in conditions
@
text
@d1 4
a4 4
make: "cond-token-number.mk" line 15: Malformed conditional (-0)
make: "cond-token-number.mk" line 25: Malformed conditional (+0)
make: "cond-token-number.mk" line 35: Malformed conditional (!-1)
make: "cond-token-number.mk" line 45: Malformed conditional (!+1)
@


1.5
log
@make: clean up comments
@
text
@a4 1
make: "cond-token-number.mk" line 89: End of the tests.
@


1.4
log
@make(1): add remarks to the tests about conditions
@
text
@d5 1
a5 1
make: "cond-token-number.mk" line 80: End of the tests.
@


1.3
log
@make(1): add test for hexadecimal numbers in conditionals
@
text
@d1 5
a5 5
make: "cond-token-number.mk" line 13: Malformed conditional (-0)
make: "cond-token-number.mk" line 21: Malformed conditional (+0)
make: "cond-token-number.mk" line 29: Malformed conditional (!-1)
make: "cond-token-number.mk" line 37: Malformed conditional (!+1)
make: "cond-token-number.mk" line 70: End of the tests.
@


1.2
log
@make(1): add tests for numbers in conditions
@
text
@d5 1
a5 1
make: "cond-token-number.mk" line 54: End of the tests.
@


1.1
log
@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.
@
text
@d1 8
a8 1
exit status 0
@