X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
Subject: Re: __STRICT_ANSI__ and excluded definitions
To: djgpp AT delorie DOT com
References: <xnczzu3f5z DOT fsf AT envy DOT delorie DOT com>
From: "Andris Pavenis (andris DOT pavenis AT iki DOT fi) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Message-ID: <24514c64-0ebf-96cc-4db6-89beb7a1fcdf@iki.fi>
Date: Mon, 30 Nov 2020 20:25:13 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.4.3
MIME-Version: 1.0
In-Reply-To: <xnczzu3f5z.fsf@envy.delorie.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US-large
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from Quoted-Printable to 8bit by delorie.com id 0AUIPrIk013454
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 11/30/20 7:52 PM, DJ Delorie wrote:
> Best thing to do is to file a bug with gcc and let them language-lawyer
> it out.

I mentioned as example the behavior in Linux. In this case its glibc implementation stuff not even 
gcc one:

- gcc or clang only defines __STRICT_ANSI__

- glibc headers causes definitions of pid_t and ino_t and other stuff not to be excluded

Another question whether specifying for example -std=c++11 (which implies __STRICT_ANSI__) also 
implies ANSI C  for used C headers.

We have also disabled excluding some definitions when both __STRICT_ANSI__ and __plusplus are 
defined in some places (for example stdio.h)


Andris