| History log of /src/usr.bin/make/unit-tests/varmod-mtime.exp |
| Revision | | Date | Author | Comments |
| 1.16 |
| 28-Jun-2025 |
rillig | 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.
|
| 1.15 |
| 12-Jun-2025 |
rillig | make: use a common style for unexpected error messages
In enomem, report the actual error instead of a fixed ENOMEM.
|
| 1.14 |
| 30-Mar-2025 |
rillig | 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.
|
| 1.13 |
| 29-Mar-2025 |
rillig | make: add ":" to error message about unknown modifier
In the manual page, the modifiers are listed with a preceding ":", so
use the same pattern in the error message. This removes an inconsistency
between the error messages "Unknown modifier" and "Bad modifier".
|
| 1.12 |
| 11-Jan-2025 |
rillig | make: omit redundant follow-up message "Malformed conditional"
If there is a parse error or an evaluation error during the conditional,
the conditional is already mentioned in the "while evaluating condition"
line, so there's no reason to repeat it once again.
Same for the "Bad condition" message from the '?:' modifier.
|
| 1.11 |
| 29-Aug-2024 |
rillig | make: reduce line length in error messages
The error messages for deeply nested parse errors were hard to decipher,
due to the large amount of text. Split these messages into individual
lines, just as in the backtrace for .include files and .for loops. This
unified backtrace makes the output more uniform.
|
| 1.10 |
| 06-Aug-2024 |
rillig | make: in error message about conditionals, use single quotes
Single quotes are used less often in the conditionals themselves, which
leads to fewer confusions.
|
| 1.9 |
| 04-Jul-2024 |
rillig | make: add more context information to error messages
In case of a parse error or evaluation error, print the variable value
in addition to the variable name, to see the effects of previous
expression modifiers.
In nested make calls, print the current directory at the bottom of a
stack trace, as that information is otherwise hard to get in a parallel
build spanning multiple directories.
|
| 1.8 |
| 20-Apr-2024 |
rillig | branches: 1.8.2;
make: provide more context information for parse/evaluate errors
|
| 1.7 |
| 19-Nov-2023 |
rillig | tests/make: cover all code paths for the ':mtime' modifier
|
| 1.6 |
| 19-Nov-2023 |
rillig | make: produce more accurate error message for invalid ':mtime' argument
|
| 1.5 |
| 19-Nov-2023 |
rillig | tests/make: test non-integer fallback in ':mtime' modifier
|
| 1.4 |
| 19-Aug-2023 |
sjg | varmod-mtime.mk: use :localtime for %s
Add a comment to explain why ${%s:L:localtime} should be used to get
a value that matches time(3).
|
| 1.3 |
| 17-Aug-2023 |
rillig | make: be strict when parsing the argument of the ':mtime' modifier
|
| 1.2 |
| 17-Aug-2023 |
rillig | tests/make: extend tests for the ':mtime' modifier
|
| 1.1 |
| 09-May-2023 |
sjg | make: add :mtime to provide mtime of file
The value of the variable is passed to stat(2)
and st_mtime is new value.
An optional arg can be used if stat(2) fails, otherwise
the current time is used.
See varmod-mtime.mk for usage examples.
|
| 1.8.2.1 |
| 02-Aug-2025 |
perseant | Sync with HEAD
|
