This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: included file in std_algorithm.h
- From: Benjamin Kosnik <bkoz at redhat dot com>
- To: Jeffrey Turner <jturner at mail dot alum dot rpi dot edu>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Mon, 31 Dec 2001 10:21:06 -0800 (PST)
- Subject: Re: included file in std_algorithm.h
> #include <bits/c++config.h>
>
> However, the only file in bits which comes close is
> c++config [nb: no .h]. I suppose that shows the
> importance of _that_ header file.
Constructed at build time. See include/Makefile.am.
If you do any work with headers, you must understand the configure and build
procedure. It's crucial, as configure options change what is built.
> BTW, I am working on updating the whole libstdc++
> in both programming style and the use of #includes
> which someone mentioned should only be in the
> standard library files.
Uh. You might want to outline your proposed effort before going too far
down this path.
> One other question, why are the files referred to
> by <cxxxxxx> in one (or is it two) separate directories
> from the other <xxxxxxx> C++ standard headers?
> What differentiates c_std from c_shadow? I think it
> might be wise as a hint to put the carry-over, non-
> namespace C headers in include/deprecated, any thoughts?
May I suggest reading the README, as well as the other documentation?
-benjamin