[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BASH_SUBSHELL documentation misleading
From: |
Clark J. Wang |
Subject: |
Re: BASH_SUBSHELL documentation misleading |
Date: |
Fri, 25 Mar 2011 10:10:59 +0800 |
On Fri, Mar 25, 2011 at 2:17 AM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:
> On Thu, Mar 24, 2011 at 06:07:33PM +0000, Marc Herbert wrote:
> > Not every feature is complicated enough that it requires special
> > documentation care and that it raises a discussion here.
>
> BASH_SUBSHELL isn't complicated at all. It's just documented in a
> confusing way. It doesn't require an example to say that it reports the
> current subshell depth. It's just that the existing documentation
> can be interpreted to make someone think that it tracks a running total
> of how many subshells were created as children of the current shell in
> the past. That's where Sam got mixed up.
>
>
Agree. It's not complicated compared to, for example, =~ usage. :)
--
Clark J. Wang
- BASH_SUBSHELL documentation misleading, Sam Liddicott, 2011/03/23
- Re: BASH_SUBSHELL documentation misleading, Chris F.A. Johnson, 2011/03/23
- Re: BASH_SUBSHELL documentation misleading, Sam Liddicott, 2011/03/23
- Re: BASH_SUBSHELL documentation misleading, Marc Herbert, 2011/03/24
- Re: BASH_SUBSHELL documentation misleading, Greg Wooledge, 2011/03/24
- Re: BASH_SUBSHELL documentation misleading, Marc Herbert, 2011/03/24
- Re: BASH_SUBSHELL documentation misleading, Greg Wooledge, 2011/03/24
- Re: BASH_SUBSHELL documentation misleading,
Clark J. Wang <=
- Re: BASH_SUBSHELL documentation misleading, Maarten Billemont, 2011/03/23