[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: return exit code in EXIT trap
From: |
Chet Ramey |
Subject: |
Re: return exit code in EXIT trap |
Date: |
Tue, 2 Aug 2022 16:57:05 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 |
On 8/2/22 4:18 PM, Robert E. Griffith wrote:
The first (getyarn...) link renders as a blank page for me. What it is
supposed to be?
https://getyarn.io/yarn-clip/cea30edb-a7a6-465b-bc51-3d53d9281447
Is there a reason why POSIX would want the return behavior to of function
down the stack to behave differently when in a trap? Seems strange to me.
I don't remember if Koichi ever opened up a bug with the Austin Group.
Until then, I'm going by the plain language of the standard. It seems more
strange that POSIX would have intended this to mean only a `return' in the
actual action string (A) instead of while the trap action is executing (B).
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
- return exit code in EXIT trap, Robert E. Griffith, 2022/08/02
- Re: return exit code in EXIT trap, Chet Ramey, 2022/08/02
- Re: return exit code in EXIT trap, Robert E. Griffith, 2022/08/02
- Re: return exit code in EXIT trap,
Chet Ramey <=
- Re: return exit code in EXIT trap, Robert E. Griffith, 2022/08/02
- Re: return exit code in EXIT trap, Koichi Murase, 2022/08/02
- Re: return exit code in EXIT trap, Robert E. Griffith, 2022/08/03
- Re: return exit code in EXIT trap, Koichi Murase, 2022/08/05
- Re: return exit code in EXIT trap, Robert E. Griffith, 2022/08/06
- Re: return exit code in EXIT trap, Robert Elz, 2022/08/06
- Re: return exit code in EXIT trap, Robert E. Griffith, 2022/08/06
- Re: return exit code in EXIT trap, Koichi Murase, 2022/08/06
- Re: return exit code in EXIT trap, Robert Elz, 2022/08/06
- Re: return exit code in EXIT trap, Robert E. Griffith, 2022/08/06