From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-workers@zsh.org>
Subject: Re: [Bug] Exiting shell from function called by trap handler always produces status 0
Date: Tue, 9 Oct 2018 14:50:50 +0100 [thread overview]
Message-ID: <20181009135052eucas1p14cda585c1e29330148c16707b9dbd54e~b9Pn0pHXL2830528305eucas1p1o@eucas1p1.samsung.com> (raw)
In-Reply-To: <1539092591.3286.12.camel@samsung.com>
On Tue, 2018-10-09 at 14:43 +0100, Peter Stephenson wrote:
> On Tue, 2018-10-09 at 13:39 +0000, Daniel Shahaf wrote:
> > Peter Stephenson wrote on Tue, 09 Oct 2018 14:16 +0100:
> > A function-local 'static' (below) is implicitly initialized to 0, but
> > a non-static global is not implicitly initialized.
> If that's really the case then the entire shell (look around at other
> cases), and pretty much every other non-trivial programme I've ever
> written, is fundamentally broken. I'm not going to try to fix that now.
>
> I can't quote chapter and verse but in all interesting cases they're
> initialised to zero.
Looking around at some discussions of this subject on websites...
I wonder if you're getting confused between static and automatic
*allocation* vs. global and static *linkage*? Linkage has no effect
here: global variables are statically allocated.
pws
next prev parent reply other threads:[~2018-10-09 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181009012624epcas1p44f2ae223f663713a980af4be735e5a3f@epcas1p4.samsung.com>
2018-10-08 13:02 ` Martijn Dekker
2018-10-09 8:49 ` Peter Stephenson
2018-10-09 9:58 ` Mikael Magnusson
2018-10-09 11:46 ` Martijn Dekker
2018-10-09 13:16 ` Peter Stephenson
2018-10-09 13:39 ` Daniel Shahaf
2018-10-09 13:43 ` Peter Stephenson
[not found] ` <1539092591.3286.12.camel@samsung.com>
2018-10-09 13:50 ` Peter Stephenson [this message]
2018-10-09 20:09 ` Peter Stephenson
2018-10-10 8:56 ` Daniel Shahaf
2018-10-10 9:31 ` 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='20181009135052eucas1p14cda585c1e29330148c16707b9dbd54e~b9Pn0pHXL2830528305eucas1p1o@eucas1p1.samsung.com' \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/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).