public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: EAPI 3 and "nonfatal die"
Date: Mon, 24 Aug 2009 23:16:58 +0100	[thread overview]
Message-ID: <20090824231658.3224df06@snowmobile> (raw)
In-Reply-To: <4A930FB0.5010309@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]

On Mon, 24 Aug 2009 15:09:52 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> > I'd like die to respect nonfatal.  People using nonfatal should
> > check beforehand that the functions they're calling won't do
> > anything stupid if die's are ignored.
> 
> If you're doing that then it might be wise to add an 'assert' helper
> that is guaranteed to generate an exception regardless of 'nonfatal'
> status.

Probably not the best choice of name... 'assert' is already in use for
checking PIPESTATUS.

The other problem with doing things that way is that people have to
start writing code that does an EAPI check just to be able to force a
die. An IGNORE_NONFATAL environment variable, whilst slightly ickier,
avoids that issue if we do change the definitions of die and nonfatal.

*shrug* I still think the way it was originally worded is the best
option. Otherwise we'll just replace the "some helpers die, some don't,
and no-one knows which" situation with "some eclass functions are
nonfatal aware, some aren't, and no-one knows which", with an added
side helping of "people need to find out whether any of the callers in
any overlay anywhere expect this function to work with nonfatal before
changing it".

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2009-08-24 22:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 20:56 [gentoo-dev] EAPI 3 and "nonfatal die" David Leverton
2009-08-21 21:09 ` Maciej Mrozowski
2009-08-21 21:12   ` Ciaran McCreesh
2009-08-21 23:01     ` Maciej Mrozowski
2009-08-21 23:06       ` Ciaran McCreesh
2009-08-21 23:20         ` Maciej Mrozowski
2009-08-21 23:26           ` Ciaran McCreesh
2009-08-21 21:34 ` [gentoo-dev] " David Leverton
2009-08-21 22:40 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
2009-08-21 22:51   ` Ciaran McCreesh
2009-08-21 23:15     ` Arfrever Frehtes Taifersar Arahesis
2009-08-21 23:28       ` Ciaran McCreesh
2009-08-21 23:39         ` Arfrever Frehtes Taifersar Arahesis
2009-08-21 23:43           ` Ciaran McCreesh
2009-08-23  2:48             ` Arfrever Frehtes Taifersar Arahesis
2009-08-23 15:19               ` Ciaran McCreesh
2009-08-22  2:46 ` [gentoo-dev] " Ryan Hill
2009-08-24 18:20   ` Christian Faulhammer
2009-08-24 19:02     ` Thomas Anderson
2009-08-25 10:21     ` Marijn Schouten (hkBst)
2009-08-25 11:35       ` Ciaran McCreesh
2009-08-24 22:09   ` Zac Medico
2009-08-24 22:16     ` Ciaran McCreesh [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=20090824231658.3224df06@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-dev@lists.gentoo.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