Re: [Help-bash] Why `echo !(*.l).c` behaves different depending on the context?

[Peng Yu]

> This makes no sense at all. Whether or not the shell parses each command
> in, say, the body of a compound command one at a time (it does, but they
> are all part of the same command list), it cannot execute any of them until
> the entire compound command is parsed successfully. Would you want the
> test in an if statement to be executed, and commands executed on the fly
> as they are encountered, without a trailing `fi'?

Then, you can make it fail (and possibly roll back before the
if-statement). I don't think it is absolutely impossible to do. It is
just probably difficult to do with the current framework.

-- 
Regards,
Peng