C++Intro(3)

πŸ’– C++Intro πŸ’–

okay bestie, welcome to C++Intro from the Standard C++ Library β€” this is your little doorway into the GNU libstdc++ man pages 🫢


✨ NAME ✨

C++Intro β€” a whole intro to the GNU libstdc++ man pages, fr fr πŸ’…


🌸 DESCRIPTION 🌸

So this man page is basically the welcome mat for the GNU implementation of the Standard C++ Library. It's short on purpose. If you want a real intro and the full tea, go check the libstdc++ homepage β€” it's linked at the bottom, iykyk ✨

Every single standard library entity lives inside namespace std, and its man page starts with "std::". Like, if you wanna read up on the template class std::vector, you literally just type:

man std::vector

Iconic. But heads up β€” some entities don't have their own separate man page, and for those you gotta go look at the big listing in man Namespace_std. No cap. πŸ™ˆ

Also, every one of these man pages is automatically generated by Doxygen. If you wanna know more about that tool, peep the HTML counterpart to these man pages. πŸŽ€

And some man pages aren't about one single class or function at all β€” they're describing whole categories of the Standard Library. (If you want a way more thorough intro to all these categories, go read a text like Josuttis' or Austern's. That's the homework, bestie. πŸ“š) These category pages are:

  • C++Intro β€” this page. hiii that's us 🫢
  • Namespace_std β€” a listing of the contents of std::.
  • Namespace___gnu_cxx β€” a listing of the contents of __gnu_cxx::.
  • Containers β€” an introduction to container classes.
  • Sequences β€” linear containers.
  • Assoc_containers β€” key-based containers.
  • Iterator_types β€” programatically distinguishing iterators/pointers.
  • Intro_functors β€” an introduction to function objects, or functors.
  • Arithmetic_functors β€” functors for basic math.
  • Binder_functors β€” functors which "remember" an argument.
  • Comparison_functors β€” functors wrapping built-in comparisons.
  • Func_ptr_functors β€” functors for use with pointers to functions.
  • Logical_functors β€” functors wrapping the Boolean operations.
  • Member_ptr_functor β€” functors for use with pointers to members.
  • Negation_functors β€” functors which negate their contents.
  • SGIextensions β€” a list of the extensions from the SGI STL subset.

The HTML documentation typically goes into much more depth. So if you're a details girlie, that's your lane. πŸ’œ


πŸ“ FILES πŸ“

Lots! 😭 (yes that's the whole answer, she's mysterious)

πŸ“ Standard Headers

These headers will be found automatically, unless you instruct the compiler otherwise. ✨

<algorithm>  <csignal>     <iomanip>   <ostream>
<bitset>     <cstdarg>     <ios>       <queue>
<cassert>    <cstddef>     <iosfwd>    <set>
<cctype>     <cstdio>      <iostream>  <sstream>
<cerrno>     <cstdlib>     <istream>   <stack>
<cfloat>     <cstring>     <iterator>  <stdexcept>
<ciso>646    <ctime>       <limits>    <streambuf>
<climits>    <cwchar>      <list>      <string>
<clocale>    <cwctype>     <locale>    <utility>
<cmath>      <deque>       <map>       <valarray>
<complex>    <fstream>     <memory>    <vector>
<csetjmp>    <functional>  <numeric>

πŸ¦‹ Backwards-Compatibility Headers

For GCC 3.0 these headers will be found automatically, unless you instruct the compiler otherwise. But do NOT depend on this β€” instead you should read FAQ 5.4 and use a backward/ prefix. that's the rule, periodt πŸ’…

<strstream>

🧚 Extension Headers

These headers will only be found automatically if you include the leading ext/ in the name. Otherwise you need to read FAQ 5.4. πŸ‘‘

<ext/algorithm>            <ext/numeric>
<ext/functional>           <ext/iterator>
<ext/slist>                <ext/rb_tree>
<ext/rope>                 <ext/memory>
<ext/bitmap_allocator.h>   <ext/debug_allocator.h>
<ext/malloc_allocator.h>   <ext/mt_allocator.h>
<ext/pool_allocator.h>     <ext/pod_char_traits.h>
<ext/stdio_filebuf.h>      <ext/stdio_sync_filebuf.h>

🌈 Libraries

  • libstdc++.a β€” the library implementation in static archive form. If you didn't configure libstdc++ to use shared libraries, this one will always be used. Otherwise it only gets used if the user asks for it. ✨
  • libsupc++.a β€” this library contains C++ language support routines. Usually you will never need to know about it, but it can be useful. See FAQ 2.5. 🫢
  • libstdc++.so[.N] β€” the library implementation in shared object form. By default this gets used in preference to the static archive form. N will be a number equal to or greater than 3. But if N is in the 2.x series, then you are looking at the old libstdc++-v2 library, which we do not maintain. πŸ’€
  • libstdc++.la
  • libsupc++.la β€” these are Libtool library files, and should only be used when working with that tool.

πŸ‘‘ CONFORMING TO πŸ‘‘

Almost conforming to International Standard ISO/IEC 14882:1998(E), Programming Languages --- C++ (aka the C++ standard), in addition to corrections proposed by the Library Working Group, JTC1/SC22/WG21. slay πŸ’…


⭐ SEE ALSO ⭐

http://gcc.gnu.org/libstdc++/ for the Frequently Asked Questions, online documentation, and much, much more! πŸ”₯


and that's the whole page, bestie 🌸 this was C++Intro(3) from GNU libstdc++, dated 20 May 2004 β€” go be the main character of your own compile errors πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from