From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id DCBD61F8C2;
	Sun,  7 Feb 2021 23:10:20 +0000 (UTC)
Date: Sun, 7 Feb 2021 23:10:20 +0000
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: dprintf(3) portability? [was [02/19] spawn: pi_fork_exec: support
 "pgid"]
Message-ID: <20210207231020.GA3462@dcvr>
References: <20210207085201.13871-1-e@80x24.org>
 <20210207085201.13871-3-e@80x24.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20210207085201.13871-3-e@80x24.org>
List-Id: <meta.public-inbox.org>

Eric Wong <e@80x24.org> wrote:
> +++ b/lib/PublicInbox/Spawn.pm

> +		/* continue message started by exit_err in child */
> +		dprintf(err_fd, ": %s\n", strerror(cerrnum));

dprintf(3) is POSIX.1-2008 and we already depend on Perl 5.10.1
from 2009, so no concerns there, right?

I remember it being a portability problem around 2004, but it's
probably not an issue today.  This usage is trivial enough to
replace with writev(2), though.