Hi Eric,

> As we learned in autoconf, exploiting syntax extensions (like a[b]=c
> or ${1//a/b}) must be hidden behind eval, otherwise, shells that do
> not understand the extensions will get lost when trying to parse to
> the end of the statement, even if the shell will never execute the
> extension because cond was false.

Thanks for this fix. I try to minimize the use of 'eval', but here it
is necessary, and the effects of 'eval' on a single-quoted string are
easy to understand.

Bruno

Reply via email to