about summary refs log tree commit diff
path: root/Doc
diff options
context:
space:
mode:
authorPeter Stephenson <p.w.stephenson@ntlworld.com>2014-09-18 19:09:52 +0100
committerPeter Stephenson <p.w.stephenson@ntlworld.com>2014-09-18 19:09:52 +0100
commit08e5191ff016f9df61bb157fc56cb9af6c599863 (patch)
tree70f0c8e0b4c351db1c979aff8b2d0c805f8cb9cd /Doc
parent9c29a4f1f6297d97d4644b074f7246b980751e2b (diff)
downloadzsh-08e5191ff016f9df61bb157fc56cb9af6c599863.tar.gz
zsh-08e5191ff016f9df61bb157fc56cb9af6c599863.tar.xz
zsh-08e5191ff016f9df61bb157fc56cb9af6c599863.zip
users/19097: remove $functypetrace in favour of ref to $zsheval_context
Diffstat (limited to 'Doc')
-rw-r--r--Doc/Zsh/mod_parameter.yo22
1 files changed, 9 insertions, 13 deletions
diff --git a/Doc/Zsh/mod_parameter.yo b/Doc/Zsh/mod_parameter.yo
index c1571603c..09ceba258 100644
--- a/Doc/Zsh/mod_parameter.yo
+++ b/Doc/Zsh/mod_parameter.yo
@@ -201,10 +201,7 @@ The format of each element is var(filename)tt(:)var(lineno).
 For functions autoloaded from a file in native zsh format, where only the
 body of the function occurs in the file, or for files that have been
 executed by the tt(source) or `tt(.)' builtins, the trace information is
-shown as var(filename)tt(:)var(0), since the entire file is the
-definition.
-
-The most recent call is the first element in the array.
+shown as var(filename)tt(:)var(0), since the entire file is the definition.
 
 Most users will be interested in the information in the
 tt(funcfiletrace) array instead.
@@ -215,6 +212,14 @@ This array contains the names of the functions, sourced files,
 and (if tt(EVAL_LINENO) is set) tt(eval) commands. currently being
 executed. The first element is the name of the function using the
 parameter.
+
+The standard shell array tt(zsh_eval_context) can be used to
+determine the type of shell construct being executed at each depth:
+note, however, that is in the opposite order, with the most recent
+item last, and it is more detailed, for example including an
+entry for tt(toplevel), the main shell code being executed
+either interactively or from a script, which is not present
+in tt($funcstack).
 )
 vindex(functrace)
 item(tt(functrace))(
@@ -224,13 +229,4 @@ The format of each element is var(name)tt(:)var(lineno).
 Callers are also shown for sourced files; the caller is the point
 where the tt(source) or `tt(.)' command was executed.
 )
-vindex(functypestack)
-item(tt(functypestack))(
-This array corresponds element by element with tt(funcstack).
-Each element contains `tt(source)' for a sourced file, `tt(function)'
-for a function and `tt(eval)' for an tt(eval)'d expression.  At the top
-level of execution of a series of commands, tt($functypestack[1]) is
-empty if the commands are being executed as a script, or one of the
-previous strings if the commands are being executed as that type.
-)
 enditem()