From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from vultr.musolino.id.au ([45.76.123.158]) by ewsd; Wed Oct 21 00:09:04 -0400 2020
Received: from 203.53.188.82 ([203.53.188.82]) by vultr; Wed Oct 21 04:08:20 +0000 2020
Message-ID: <14F31F6EA805615CEA96977406C71209@musolino.id.au>
From: Alex Musolino <alex@musolino.id.au>
Date: Wed, 21 Oct 2020 14:38:20 +1030
To: 9front@9front.org
Subject: Re: [9front] libmp and error handling
In-Reply-To: <D61860A06A3D437F1980A9EDAC27510F@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: responsive asynchronous general-purpose self-signing JSON configuration standard persistence database 

> There's both an easy way and a hard way to fix this.  The easy way
> would be to document the sysfatal call in the manpage and mention
> that sysfatal should be overridden in order to change the error
> handling.  The hard way would be to remove the sysfatal calls in
> libmp, then change the rest of the system so that it catches the
> errors.

Or split the difference and introduce something like Blethal(2).  Then
change the existing programs (less than 40 by my count) to supply
sysfatal as the handler.