What is the name of the library connecting all the libraries in c ++?

Closed due to the fact that the essence of the issue is not clear to the participants Cheg , αλεχολυτ , Harry , Vladimir Gamalyan , aleksandr barakin 24 Sep '17 at 0:06 .

Try to write more detailed questions. To get an answer, explain what exactly you see the problem, how to reproduce it, what you want to get as a result, etc. Give an example that clearly demonstrates the problem. If the question can be reformulated according to the rules set out in the certificate , edit it .

  • Yes there is no such ... - Harry
  • there is one, but I don’t remember what it is called - han joker
  • four
    I think it’s about stdafx.h - KoVadim
  • @KoVadim, this is not a library at all. - ߊߚߤߘ
  • one
    I know. But this header can really connect a lot of things. - KoVadim

2 answers 2

(Although I suspect that the TS calls the library header (.h) the file included by the #include directive, I will answer formally, as if the question was really about libraries, i.e., from where the linker takes functions when creating the executable module whose prototypes are described in the very headers)

The library (ELF file .so in * nix or .dll in windows), which connects everything, of course, does not exist.

Probably one of the main C ++ libraries that is connected to all programs in this language is libstdc++.so

You can also notice that the main (in the same sense) library in the system is libc - this is where all the basic functions are located that use all the functions of all libraries of all languages ​​(at least to call OS functions implemented in the kernel).

    I think it meant <bits/stdc++.h>

    Used in Olympiad programming, not to write a lot of #include

    This header is not part of the standard, and therefore only works in g ++, but does not work in Visual Studio.