Also in parse_matched_pair:
diff --git a/parse.y b/parse.y
index 0a8c039a..1001ac1b 100644
--- a/parse.y
+++ b/parse.y
@@ -3906,14 +3906,13 @@ parse_matched_pair (int qc, int open, int
close, size_t *lenp, int flags)
/* Locale expand $"..." here. */
/* PST_NOEXPAND */
ttrans =
./bash --norc -O noexpand_translation -in <<<'$":"'
=ERROR: AddressSanitizer: heap-use-after-free on address 0x000108102b40
READ of size 1 thread T0
#0 read_token_word parse.y:5236
#1 read_token parse.y:3618
freed by thread T0 here:
#1 read_token_word parse.y:5231
#2 read_token
Chet Ramey writes:
> If they're linked, why wouldn't saying filename generation isn't performed
> be enough to imply that brace expansion isn't performed either?
Hmm, yes, good point.
Dale
On 3/15/23 12:52 AM, Alex Bochannek wrote:
Chet,
Thank you for the thoughtful responses. My thoughts below got a bit
long, so here is a summary:
- The here-string documentation should either spell out that brace
expansion is not performed or simple only list the expansions that
are.
On Wed, Mar 15, 2023, 8:07 AM Robert Elz wrote:
> While it is probably useful to have every place where expansions occur list
> which ones apply, perhaps it would (also) be useful to include the general
> principle which controls all of this.
>
> That is, expansions are performed, late (just as
While it is probably useful to have every place where expansions occur list
which ones apply, perhaps it would (also) be useful to include the general
principle which controls all of this.
That is, expansions are performed, late (just as commands are about to
be run, after all parsing has
