This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFC / patch] Autoconf test to avoid inclusion of <cstdio>

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Theodore Papadopoulo <Theodore dot Papadopoulo at sophia dot inria dot fr>
Cc: libstdc++ at gcc dot gnu dot org
Date: Thu, 7 Aug 2008 05:31:42 -0500 (CDT)
Subject: Re: [RFC / patch] Autoconf test to avoid inclusion of <cstdio>
Accept-language: en-US
References: <21042076.1218042604718.JavaMail.oracle@acsmt302.oracle.com> <21439388.1218045414211.JavaMail.oracle@acsmt302.oracle.com> <29977346.1218058604607.JavaMail.oracle@acsmt302.oracle.com> <489AC45B.9010409@sophia.inria.fr>

Hi,

> Why don't you just use autoconf to generate a small header
> with the proper definitions of your _IOS_BASE_* macros. That would totally avoid the reference to
> cstdio (except for the cases where target!=host).

thanks Theodore, this is a very nice suggestion, generating an header with autoconf! I'm sure that sooner or later we'll put it good use. First, however, very pragmatically, I would like to ask, in particular to the readers of this list, how many targets are known to have EOF != -1, SEEK_CUR != 1 and SEEK_END != 2... I suspect powerful approaches like yours are a bit overkill here...

Paolo.

References:
- [RFC / patch] Autoconf test to avoid inclusion of <cstdio>
  - From: Paolo Carlini
- Re: [RFC / patch] Autoconf test to avoid inclusion of <cstdio>
  - From: Paolo Carlini
- Re: [RFC / patch] Autoconf test to avoid inclusion of <cstdio>
  - From: Paolo Carlini
- Re: [RFC / patch] Autoconf test to avoid inclusion of <cstdio>
  - From: Theodore Papadopoulo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]