On Mon, Mar 10, 2003 at 10:44:34 -0500, Mike Barcroft wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
Many programs (from ports too) defines _ISOC99_SOURCE to get C99
functions, but we don't sense this define currently. Here is the fix for
review:
Cool. I didn't realize there was
Andrey A. Chernov [EMAIL PROTECTED] writes:
Hm, I don't quite understand, which one part you mean? My patch handles
2 following cases:
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
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
Andrey A. Chernov [EMAIL PROTECTED] writes:
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
On Tue, 11 Mar 2003 19:42:41 +0300, Andrey A. Chernov [EMAIL PROTECTED] said:
What to do, if, say, C99 program want to use some POSIX functions from
lower (and not from higher) POSIX standard?
Programmer error. Either it's a C99 program or it's an old-POSIX
program; it cannot be both.
Andrey A. Chernov [EMAIL PROTECTED] writes:
Many programs (from ports too) defines _ISOC99_SOURCE to get C99
functions, but we don't sense this define currently. Here is the fix for
review:
Cool. I didn't realize there was an existing precedence, or I would
have used it.
--- cdefs.h.bak
Many programs (from ports too) defines _ISOC99_SOURCE to get C99
functions, but we don't sense this define currently. Here is the fix for
review:
--- cdefs.h.bak Wed Oct 23 05:04:06 2002
+++ cdefs.h Mon Mar 10 09:11:01 2003
@@ -360,6 +360,9 @@
#define__POSIX_VISIBLE 198808
