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] libstdc++/6720 and libstdc++/6671


Mark Mitchell <mark@codesourcery.com> writes:

| --On Wednesday, May 22, 2002 09:48:57 PM +0200 Gabriel Dos Reis 
| <gdr@codesourcery.com> wrote:
| 
| > Mark Mitchell <mark@codesourcery.com> writes:
| >
| > [...]
| >
| >| If we had a directory that contained *only* the standard headers, i.e,.
| >| <cmath>, <cstdio>, <iostream>, etc., then could we just put it at
| >| the front of the #include path?  In other words, *prepend*
| >| -I /path/to/dir to the front of the users command line?
| >
| > I think that will work for standard headers.  How can we make that
| > work with extension headers?
| 
| Well, for them, we don't have a standards issue; it's at most a QOI
| issue.
| 
| So, maybe we don't need to worry about it?

That is OK by me.

| (I'm not even sure the extension headers should be named "memory" and
| so forth; maybe they should be "memory.h".  They're not the magic headers
| defined by the standard; they're just headers we provide as part of our
| implementation.)

This has been discussed in the past and the majority voted for having
extension for extension headers :-)  So, no problem.

-- Gaby


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