Re: [PATCH v3 10/12] usage: allow dying without writing an error message

From: Karthik Nayak <karthik.188@gmail.com>
Date: Jun 3, 2025, 09:04 UTC
Message-ID: <CAOLa=ZQTYTNiUhFW+kOqMro0rpWVTkyKop7az_6h7zgM8njRhw@mail.gmail.com>
In-Reply-To: <256e9e60-fdea-461b-b43c-8e6024b773a2@app.fastmail.com>

On Tue, Jun 3, 2025 at 10:34 AM Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:

Show 11 quoted lines

>
> On Tue, Jun 3, 2025, at 10:31, Karthik Nayak wrote:
> > Patrick Steinhardt <ps@pks.im> writes:
> >
> >> Sometimes code wants to die in a situation where it already has written
> >> an error message. To use the same error code as `die()` we have to open
> >> code the code with a call to `exit(128)` in such cases, which is easy to
> >
> > Nit: This reads a little weird.
>
> Maybe s/to open code the code/to open-code the code/

Ah, that makes so much difference.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.