From owner-freebsd-questions@FreeBSD.ORG  Tue Nov 18 01:57:13 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 79A9D5E0
 for <freebsd-questions@freebsd.org>; Tue, 18 Nov 2014 01:57:13 +0000 (UTC)
Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3B94D8AB
 for <freebsd-questions@freebsd.org>; Tue, 18 Nov 2014 01:57:13 +0000 (UTC)
Received: from r56.edvax.de (port-92-195-158-193.dynamic.qsc.de
 [92.195.158.193])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx01.qsc.de (Postfix) with ESMTPS id B0C1A3CD91;
 Tue, 18 Nov 2014 02:57:09 +0100 (CET)
Received: from r56.edvax.de (localhost [127.0.0.1])
 by r56.edvax.de (8.14.5/8.14.5) with SMTP id sAI1v7mN002069;
 Tue, 18 Nov 2014 02:57:08 +0100 (CET)
 (envelope-from freebsd@edvax.de)
Date: Tue, 18 Nov 2014 02:57:07 +0100
From: Polytropon <freebsd@edvax.de>
To: Doug Hardie <bc979@lafn.org>
Subject: Re: vsnprintf and friends modify the va_list argument
Message-Id: <20141118025707.fc183c55.freebsd@edvax.de>
In-Reply-To: <617C3C28-2107-4D41-9E59-4C002FBDD33D@lafn.org>
References: <C9A11AB7-0085-464E-A6FB-F6A3603B6372@lafn.org>
 <20141117030844.d83bbae3.freebsd@edvax.de>
 <617C3C28-2107-4D41-9E59-4C002FBDD33D@lafn.org>
Reply-To: Polytropon <freebsd@edvax.de>
Organization: EDVAX
X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Nov 2014 01:57:13 -0000

On Mon, 17 Nov 2014 11:15:28 -0800, Doug Hardie wrote:
> 
> > On 16 November 2014, at 18:08, Polytropon <freebsd@edvax.de> wrote:
> > Maybe adding stdarg(3) to printf(3)'s SEE ALSO section would
> > be a helpful choice here.
> 
> Probably, but I would normally never chase things that far
> to figure out there would be a problem.  I believe a warning
> like you quoted above in the printf man page would be more
> likely to be noticed.

This is probably a good and _possible_ idea. There aren't
that many va_*-related functions in the standard library,
and because the printf() family shares one manual page,
such a hint could be provided here, mentioning that because
of the use of the va_* functionality, certain arguments
will be subject to change. This is, in my opinion, a hint
that makes FreeBSD documentation more valuable again for
developers. This, in combination with the reference to
stdarg(3), could maybe be suggested to the FreeBSD doc
team.


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...