Message-ID: <20171006173420.GC76109@isc.org>
CC: 
X-Original-To: bind9-public@bugs.isc.org
Subject: Re: [ISC-Bugs #46201] Add isc_buffer_printf()
From: "Evan Hunt" <each@isc.org>
Date: Fri, 6 Oct 2017 17:34:20 +0000
X-RT-Original-Encoding: utf-8
Content-Disposition: inline
X-RT-Incoming-Encryption: Not encrypted
From each@isc.org  Fri Oct  6 17:34:21 2017
Delivered-To: bind9-public@bugs.isc.org
References: <RT-Ticket-46201@isc.org> <rt-4.4.1-21557-1507204871-466.46201-4-0@isc.org> <rt-4.4.1-22188-1507248449-60.46201-4-0@isc.org> <20171006075232.GA18759@jurassic> <rt-4.4.1-25038-1507276355-1498.46201-4-0@isc.org>
content-type: text/plain; charset="utf-8"
X-RT-Interface: Email
In-Reply-To: <rt-4.4.1-25038-1507276355-1498.46201-4-0@isc.org>
Return-Path: <each@isc.org>
Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id 167EBD78B0A for <bind9-public@bugs.isc.org>; Fri,  6 Oct 2017 17:34:21 +0000 (UTC)
Received: by bikeshed.isc.org (Postfix, from userid 10292) id DA630216C3B; Fri,  6 Oct 2017 17:34:20 +0000 (UTC)
MIME-Version: 1.0
User-Agent: Mutt/1.5.23 (2014-03-12)
To: "Mukund Sivaraman via RT" <bind9-public@isc.org>
RT-Message-ID: <rt-4.4.1-26415-1507311262-772.46201-0-0@isc.org>
Content-Length: 422

> Print to string: (s)printf
> Print to file: (f)printf
> Print to buffer: (isc_buffer_)printf

True, and I did think of that, but my brain tends to look at what's
after the last underscore as the main indicator of what a function
does, so to me isc_buffer_printf() sounds like it should print the
content of a buffer to stdout. However, since I seem to be the only
one with that quirk, I'm fine with the original name.