From owner-freebsd-audit  Mon Nov 27  7:58:42 2000
Delivered-To: freebsd-audit@freebsd.org
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105])
	by hub.freebsd.org (Postfix) with ESMTP
	id 224CE37B479; Mon, 27 Nov 2000 07:58:37 -0800 (PST)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.11.1/8.11.1) id eARG49V29464;
	Mon, 27 Nov 2000 08:04:09 -0800 (PST)
	(envelope-from sgk)
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
Message-Id: <200011271604.eARG49V29464@troutmask.apl.washington.edu>
Subject: Re: gcc __attributes for format strings
In-Reply-To: <20001126222048.A46809@citusc17.usc.edu> from Kris Kennaway at "Nov
 26, 2000 10:20:48 pm"
To: Kris Kennaway <kris@FreeBSD.ORG>
Date: Mon, 27 Nov 2000 08:04:09 -0800 (PST)
Cc: audit@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL61 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-audit@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kris Kennaway wrote:
> Okay, looks like we can play with some gcc attributes to flag things
> as format strings. For example:
> 

[snip]

> We need to go through and prototype functions appropriately (in
> headers, or internally) - I think it's possible to fix all of the
> -Wnon-const-format warnings this way.

Are gcc attributes C89 or C99 features?  If not, you probably
want to ask bde about sprinkling gcc only features throughout
the header files. 

-- 
Steve


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-audit" in the body of the message