Since inconsistency is basically "not the same rule
everywhere", it typically shows in (good) documentation. Indeed:
http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06
2.6 Word Expansions
Not all expansions are performed on every word, as explained in the
fo
On Thu, Aug 19, 2010 at 12:32 PM, Marc Herbert wrote:
> Since inconsistency is basically "not the same rule
> everywhere", it typically shows in (good) documentation. Indeed:
>
> http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html#tag_02_06
> 2.6 Word Expansions
> Not all ex
> On Thu, 12 Aug 2010 08:16:21 -0400, Greg Wooledge
>> A return that's run in a subshell doesn't cause the parent shell to
>> return.
Granted but that does not mean it should behave like "exit", instead it
could simply error like this:
$ return
bash: return: can only `return' from a function or
On Thu, Aug 19, 2010 at 11:12:03AM +0100, Marc Herbert wrote:
> > On Thu, 12 Aug 2010 08:16:21 -0400, Greg Wooledge
> >> A return that's run in a subshell doesn't cause the parent shell to
> >> return.
>
> Are there many people actually using
> "return" to exit a subshell? That would not really ma
A return that's run in a subshell doesn't cause the parent shell to
return.
**SNIP**
>> Are there many people actually using
>> "return" to exit a subshell? That would not really make code easy to
>> read.
> You misunderstood, or I was unclear.
*You* misunderstood, or I was
