TR1 and standard headers

[Jonathan Wakely]

On Sun, Oct 10, 2004 at 01:06:13AM -0500, Gabriel Dos Reis wrote:

> Matt Austern <austern@apple.com> writes:
> 
> | My apologies if Benjamin or someone else has already answered this,
> | but...
> | 
> | Have we decided on a policy yet for TR1 components that modify
> | standard headers?  TR1 defines extensions to <functional>, <utility>,
> | and probably other headers that aren't coming to mind right now.  (Not
> | counting the C99 compatibility stuff, which affects all of the <c...>
> | headers.)

I don't remember a decision.

> | 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.

jon

-- 
"Consistency requires you to be as ignorant today as you were a year ago."
	- Bernard Berenson