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] |
On Sat, 2010-01-02 at 12:26 +0000, Christopher Jefferson wrote: > 'bits' is not platform specific, but more internal details and > organisation. You shouldn't be including these headers directly, they > are all included by the appropriate proper headers. As an example, all > the <algorithm> header does is: > > #include <bits/stl_algobase.h> > #include <bits/stl_construct.h> > #include <bits/stl_uninitialized.h> > #include <bits/stl_algo.h> > > stl_algobase.h for example contains a small set of algorithms which > are used in many places (swap, min, max, copy, etc.), so other headers > can only include the parts of <algorithm> they need. > > Of course, you should NEVER include any of those headers directly, > there is no attempt to make sure you can include any of these headers > directly. > > Chris For sure. And while I know one should not directly include it, I meant under what circumstances would a developer working on their own project have such a directory? What does the "bits" stand for anyways? Thank you. -- Kip Warner -- Software Developer President & CEO Kshatra Corp. OpenPGP encrypted/signed mail preferred http://www.thevertigo.com
Attachment:
signature.asc
Description: This is a digitally signed message part
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |