Re: [9fans] x11-init.c

[Charles Forsyth <forsyth@terzarima.net>]

[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]

gcc enables the warnings with -Wformat, but the association between
varargs function and format checking is done by the following (on FreeBSD):

int	 asprintf __P((char **, const char *, ...)) __printflike(2, 3);

where

#define	__printflike(fmtarg, firstvararg) \
	    __attribute__((__format__ (__printf__, fmtarg, firstvararg)))


it's the __attribute__ cluster that's built-in to gcc.
Linux uses different #defines but the result is similar.
hence the need for ifdefs somewhere to avoid feeding __stuff__ to other compilers.
(there are many many more __things__.)
the list of formats is also built-in to the compiler.
it doesn't look as though it can easily be extended, but i have waded
through neither code nor spent time down by the docs.

Plan 9's compilers use a pragma to allow sets of format types
and flags to be defined outside the compiler, in a way that doesn't
give other compilers heartburn,
and thus without absolutely requiring ifdefs.  to be fair, the current
implementation assumes all flags (in the current scope) have the same meaning,
and does define a handful of built-in flags such as '.' (although neither restriction
is essential); 375 lines.

[-- Attachment #2: Type: message/rfc822, Size: 2790 bytes --]

From: Bengt Kleberg <bengt.kleberg@ericsson.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] x11-init.c
Date: Wed, 23 Jun 2004 08:47:20 GMT
Message-ID: <cbbe27$co0$1@newstree.wise.edt.ericsson.se>

Scott Schwartz wrote:
...deleted
> Gcc has a way to tell the compiler to check printf like varargs functions.
> Given the impact, maybe the ports should use that, at the cost of some ifdefs.

i hope this means that gcc should get some additional flags. it would be 
unfortunate if it means that the ports should be made dependent upon gcc.


bengt