Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: migrating tr1 headers for c++0x
Date: Thu, 29 May 2008 12:06:06 -0600
Message-ID: 
 <CFFDD219128FD94FB4F92B99F52D0A499AA869@exchmail01.Blue.Roguewave.Com>
Thread-Topic: migrating tr1 headers for c++0x
Thread-Index: AcjBnykdx6kq61X9R/+iYObhY7IBcQADLKVA
References: 
 <CFFDD219128FD94FB4F92B99F52D0A499AA867@exchmail01.Blue.Roguewave.Com>
 <483EC8A2.9090101@roguewave.com>
From: "Travis Vitek" <Travis.Vitek@roguewave.com>
To: <dev@stdcxx.apache.org>

=20

>Martin Sebor wrote:
>
>Travis Vitek wrote:
>> I've run into a problem while migrating the cstdint/stdint.h=20
>> headers to their new home in the include/ansi directory for
>> 4.3.x.
>>=20
>>[...]
>>
>> The problem is that the system /usr/include/stdint.h defines the
>> appropriate types [int8_t, uint8_t, ...], but it only defines
>> the limit macros [PTRDIFF_MAX, ...] if compiling as C or if=20
>> __STDC_LIMIT_MACROS is defined. So we get into the final block,
>> include the system header, but none of the macros come through.
>> At the very least this causes a bunch of failed assertions in
>> the test, but due to some minor issues with the test it actually
>> fails to compile when these macros aren't defined.
>>=20
>> Now I could easily just #define __STDC_LIMIT_MACROS for gcc before
>> including /usr/include/stdint.h [or in rw/_config-gcc.h], but that
>> wouldn't help much if the user included the system header before our
>> header.
>
>How could they do that?

Well, I would have expected that this would come up if the user did
something like this

  gcc -I/usr/include $(TOPDIR)/include/ansi \
      -I$(TOPDIR)/include $(BUILDDIR)/include -c t.cpp

I did some testing, and for some reason I can't get it to pull the
<stdint.h> from /usr/include by doing this. I guess I'm worrying about
nothing.

>
>Martin
>
>>=20