Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160610210632.ZM10619@torch.brasslantern.com>
Date: Fri, 10 Jun 2016 21:06:32 -0700
In-Reply-To: <1465580222-3300-1-git-send-email-danielsh@tarsus.local2>
Comments: In reply to Daniel Shahaf <d.s@daniel.shahaf.name>
        "[PATCH] 'functions -T' tracing: recurse into anonymous functions." (Jun 10,  5:37pm)
References: <1465580222-3300-1-git-send-email-danielsh@tarsus.local2>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] 'functions -T' tracing: recurse into anonymous functions.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jun 10,  5:37pm, Daniel Shahaf wrote:
}
}  for this function; the flag tt(-T) does the same, but turns off tracing
}  on any function called from the present one, unless that function also
} -has the tt(-t) or tt(-T) flag.  The tt(-u) and tt(-U) flags cause the
} +has the tt(-t) or tt(-T) flag or is anonymous.  The tt(-u) and tt(-U) flags cause the

That phrasing is a little hard to follow.  Perhaps something more like:

... turns off tracing
for any named (not anonymous) function called from the present one, unless
that function also ...

Note I'm also suggesting changing "turns off tracing on" into "turns off
tracing for" to reduce the chances of off/on confusion.  (Further, don't
be afraid to reformat paragraphs if lines get long.)

I've been considering something similar for the zsh/param/private module
to make caller private variables visible inside anonymous functions, but
haven't worked out all the necessary stack management.