From: "Morten Welinder" <mwelinder@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Martin Waitz" <tali@admingilde.org>,
git@vger.kernel.org
Subject: Re: SEGV when lookup_* returns NULL
Date: Mon, 27 Nov 2006 21:23:47 -0500 [thread overview]
Message-ID: <118833cc0611271823t3b1783cem38f031ac26ac0f94@mail.gmail.com> (raw)
In-Reply-To: <7v3b84e8cg.fsf@assigned-by-dhcp.cox.net>
> Why? You would certainly install your own die() handler by that
> time I presume?
Likely, but short of exiting or using longjmp/setjmp what can you do
in such a "die"? Not much. And most GUI users will be unhappy
with the exit approach.
If there is any chance that the error is not the programmer's fault, a
nice library ought to pass the error back somehow.
prev parent reply other threads:[~2006-11-28 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 21:13 SEGV when lookup_* returns NULL Martin Waitz
2006-11-27 21:55 ` Junio C Hamano
2006-11-27 23:33 ` Johannes Schindelin
2006-11-28 0:13 ` Junio C Hamano
2006-11-28 2:23 ` Morten Welinder [this message]
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=118833cc0611271823t3b1783cem38f031ac26ac0f94@mail.gmail.com \
--to=mwelinder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=tali@admingilde.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.
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).