Re: python cleanup - Mailing list pgsql-hackers

From Tom Lane
Subject Re: python cleanup
Date
Msg-id 8680.1311605563@sss.pgh.pa.us
Whole thread Raw
In response to Re: python cleanup  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: python cleanup
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 07/25/2011 10:36 AM, Tom Lane wrote:
>> Andrew Dunstan<andrew@dunslane.net>  writes:
>>> [python headers set _POSIX_C_SOURCE and _XOPEN_SOURCE]

>> BTW ... so far as I can find, there is no attempt anywhere in the
>> Postgres sources to set either of these macros.  And my understanding of
>> their purpose is that *system* headers should not be setting them at
>> all, rather the application sets them to indicate which POSIX feature
>> level it would like.  So perhaps the real question here is where the
>> heck are your conflicting values coming from ...

> _POSIX_C_SOURCE at least is defined in features.h, which is included by 
> huge numbers of system headers, many of which are included by c.h.

What is features.h, and have its authors read the POSIX standard?
AFAICS they have no business defining this symbol.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Environment checks prior to regression tests?
Next
From: Andrew Dunstan
Date:
Subject: Re: python cleanup