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: TR1 and standard headers

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Jonathan Wakely <cow at compsoc dot man dot ac dot uk>
Cc: gdr at cs dot tamu dot edu, austern at apple dot com, libstdc++ at gcc dot gnu dot org
Date: Mon, 11 Oct 2004 10:32:32 -0500
Subject: Re: TR1 and standard headers
Organization: Red Hat / Chicago
References: <A2AFE87E-1A6E-11D9-9B15-000A95BCF344@apple.com><m34ql3m7je.fsf@merlin.cs.tamu.edu><20041010174554.GA55992@compsoc.man.ac.uk>

>I don't remember a decision.

I don't either.

>> | I think we've got two sensible choices: edit the standard headers and
>> | control the extensions with a macro, or put shadow headers in
>> | include/tr1.
>> 
>> Given that TR1 is experimental by its very nature, I would think that
>> editing standard headers directly would be inappropriate.
>
>I was assuming I'd just add tr1/memory and not edit the std header, so
>users must include <tr1/memory> to get std+TR1.

Yep. That sounds best to me too. 

Shall we just go with this approach?

-benjamin

Follow-Ups:
- Re: TR1 and standard headers
  - From: Gabriel Dos Reis
- Re: TR1 and standard headers
  - From: Matt Austern

References:
- TR1 and standard headers
  - From: Matt Austern
- Re: TR1 and standard headers
  - From: Gabriel Dos Reis
- Re: TR1 and standard headers
  - From: Jonathan Wakely

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