diff options
| author | Boris Kolpackov <boris@codesynthesis.com> | 2022-12-02 15:34:53 +0200 |
|---|---|---|
| committer | Boris Kolpackov <boris@codesynthesis.com> | 2022-12-02 15:38:09 +0200 |
| commit | 649d388ff422a9a049e2b50768db357a73ee59d5 (patch) | |
| tree | 96d7acb53c56cf589d611f41aa15edd7a3cca4a0 /tests/variable/override/testscript | |
| parent | af55babfc0c01abbd0a074b0d2ed86598d6bf628 (diff) | |
Fail if scope or target qualification in variable expansion is unknown
There are three options here: we can "fall through" to an outer scope (there
is always the global scope backstop; this is the old semantics, sort of), we
can return NULL straight away, or we can fail. It feels like in most cases
unknown scope or target is a mistake and doing anything other than failing is
just making things harder to debug.
Diffstat (limited to 'tests/variable/override/testscript')
| -rw-r--r-- | tests/variable/override/testscript | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/tests/variable/override/testscript b/tests/variable/override/testscript index 9ee4643..7b973c0 100644 --- a/tests/variable/override/testscript +++ b/tests/variable/override/testscript @@ -63,6 +63,8 @@ p.x = 0 file{*}: p.x += a + file{foo}: + print $(file{foo}:p.x) p.x = 1 # Should invalidate both caches. |