Date: Tue, 11 Mar 2003 19:42:41 +0300 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Mike Barcroft <mike@FreeBSD.ORG> Cc: standards@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311164240.GA2305@nagual.pp.ru> In-Reply-To: <20030311104943.A88290@espresso.bsdmike.org> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 11, 2003 at 10:49:43 -0500, Mike Barcroft wrote: > > 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example > > (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in > > the same time. > > I don't like this at all. The meaning of _ANSI_SOURCE is that the > source is exclusively written in C89 with no BSD, POSIX, or XSI > extentions. Similarly, I was intending _C99_SOURCE to be used without > any POSIX. Programs looking for C99+POSIX functions should specify > POSIX.1-2001, which incorporates both of these. What to do, if, say, C99 program want to use some POSIX functions from lower (and not from higher) POSIX standard? Currently we have problem with ImageMagick - undefined prototypes for vsnprintf() and other like, because it wants right that: magick/studio.h: ... #define _GNU_SOURCE 1 #define _ISOC99_SOURCE 1 #define _POSIX_C_SOURCE 199506L #define _XOPEN_SOURCE 500 #define _LARGEFILE64_SOURCE 1 -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030311164240.GA2305>