From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: PATCH: test for trap EXIT fix.
Date: Mon, 01 Oct 2001 13:01:37 +0100 [thread overview]
Message-ID: <16272.1001937697@csr.com> (raw)
Here's a test that nested EXIT traps work when exiting from within a
function.
The comment notes the following behaviour:
fn() {
( trap 'print This is in the top-level function scope.' EXIT
exit
)
}
The subshell exits without ever leaving the scope of fn(), so the EXIT trap
isn't called in this case.
I'm not convinced this is wrong, or at least that it's inconsistent.
Exiting subshells is a bit of a special case.
Index: Test/C03traps.ztst
===================================================================
RCS file: /cvsroot/zsh/zsh/Test/C03traps.ztst,v
retrieving revision 1.1
diff -u -r1.1 C03traps.ztst
--- Test/C03traps.ztst 2001/04/02 12:32:43 1.1
+++ Test/C03traps.ztst 2001/10/01 11:56:41
@@ -45,6 +45,18 @@
0:Nested `trap - EXIT' on `TRAPEXIT'
>EXIT1
+# We can't test an EXIT trap for the shell as a whole, because
+# we're inside a function scope which we don't leave when the
+# subshell exits. Not sure if that's the correct behaviour, but
+# it's sort of consistent.
+ ( fn1() { trap 'print Function 1 going' EXIT; exit; print Not reached; }
+ fn2() { trap 'print Function 2 going' EXIT; fn1; print Not reached; }
+ fn2
+ )
+0:EXIT traps on functions when exiting from function
+>Function 1 going
+>Function 2 going
+
fn1() {
trap
trap 'print INT1' INT
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next reply other threads:[~2001-10-01 12:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 12:01 Peter Stephenson [this message]
2001-10-01 16:01 ` Bart Schaefer
2001-10-02 10:23 ` Peter Stephenson
2001-10-02 14:19 ` Bart Schaefer
2001-10-02 14:39 ` Peter Stephenson
2001-10-02 15:19 ` Bart Schaefer
2001-10-02 15:32 ` Peter Stephenson
2001-10-02 16:03 ` Bart Schaefer
2001-10-03 15:18 ` PATCH: (2) " Peter Stephenson
2001-10-03 16:16 ` Bart Schaefer
2001-10-08 8:10 ` Peter Stephenson
2001-10-08 9:56 ` Bart Schaefer
2001-10-08 10:32 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16272.1001937697@csr.com \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).