blocks|key|524198|text|所有C%2B%2B编译器都附带了标准模板库的某些版本。不同的编译器将支持不同版本的标准(即C%2B%2B98、C%2B%2B11、C%2B%2B14、C%2B%2B17)，但您可以期望它们都会附带诸如vector、iostream等标题。标准化过程是许多编译器供应商定义这些标头中的功能并以标准方式提供给程序员的工作，也就是说，在每个平台上都有兼容的编译器。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|524199|entityMap^0|28|6|2F|8|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

All C++ compilers ship with some version of the standard template library available to them. Different compilers will support different versions of the standards (i.e. C++98, C++11, C++14, C++17) but you can expect all of them will ship with headers like <code>vector</code>, <code>iostream</code>, etc. That's all there for you! The standardization process is an effort among many compiler vendors to define the functionality in those headers and make them available to the programmer in a standard way, that is, available in every platform there is compliant compiler for.

blocks|key|881154|text|是的，尽管对于只允许提供子集的独立实现有特殊的允许，但C%2B%2B标准库必须随每个C%2B%2B编译器一起提供，因为它是语言规范的一部分。(最初作为C%2B%2B的扩展，最初被称为标准模板库，但现在更好的术语是C%2B%2B标准库。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|881155|C%2B%2B标准库指定得非常好--您总是需要包含各种头文件才能引入标准库组件。所需的标头不会从编译器更改为编译器。在这方面，它是机器独立的。|881156|随着标准的发展，哲学是尽量减少兼容性中断，但也有一些:例如，在C%2B%2B11中对auto关键字的重新定义，以及从该标准开始对std::auto_ptr的否定。|881157|大多数组件确实在保留的命名空间std中--有些函数不是因为遗留原因。最后，最好显式地使用std:：，而不是通过使用|881158|using+namespace+std;|code-block|syntax|javascript|881159|否则，您将使代码易受命名空间歧义的影响。|881160|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Yes, notwithstanding special allowances for freestanding implementations which are permitted to provide only a subset, the C++ standard library must ship with every C++ compiler as it is part of the language specification. (What started out as an extension to C++ was originally called the standard template library but now a better term is the C++ standard library.)

The C++ standard library is extremely well specified - you always need to include various header files to bring in standard library components. The headers you need do not change from compiler to compiler. In this respect it is machine independent.

As the standard evolves the philosophy is to minimise compatibility breaks but there have been some: e.g. the redefinition of the auto keyword in C++11, and the deprecation of std::auto_ptr from that standard onwards.

Most components are indeed inside the reserved namespace std - some functions are not for legacy reasons. Finally it's better to use std:: explicitly rather than to bring in the entire std namespace into the global one by using

<pre><code>using namespace std;
</code></pre>

else you render your code vulnerable to namespace ambiguities.

blocks|key|2239538|text|标准模板库是标准模板库的一部分。因此，只要您有标准分配程序的实现，所有标准兼容编译器都可以使用它(更多信息)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2239539|由于历史原因，标准模板库在文献上被“特别”对待，C%2B%2B于1983年“诞生”，但第一个标准直到1998年才发布。|2239540|STL的第一次实现也是在1983年，但对于ADA语言。到c%2B%2B的第一个港口直到1992年惠普才完成。|2239541|1993年，建议列入ANSI标准，经一些修改后于1994年接受。|2239542|这使得stdlib上的STL成为原始STL的分叉。|2239543|在早期，有些人只使用STL来引用最初的HP库(后来由SGI维护)，而另一些人则使用STL来引用stdlib上的容器子集。|2239544|对于所有实现来说，STL外部行为应该是“相同的”，但是不同实现之间的内存打包可能有所不同。|2239545|今天，最初的C%2B%2B+STL不再被维护，谈到STL应该引用stdlib容器，尽管标准本身并不使用STL缩写。|2239546|最后，stdlib容器使用标准的分配器进行内存管理。在Linux上，它是由libstdc%2B%2B提供的，在嵌入式系统中，您需要自己为标准分配器提供一个实现，因为您没有为您管理内存的操作系统。|offset|length|2239547|这也适用于依赖系统调用的其他函数。除非您为std::cout定义了一个实现，否则它将无法在裸金属系统上使用。|style|CODE|2239548|entityMap|0|LINK|mutability|MUTABLE|url|http://en.cppreference.com/w/cpp/memory/allocator^0|0|0|0|0|0|0|0|0|G|3|0|0|L|9|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1B|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1D|8|@]|9|@$R|1E|S|1F|1|1G]]|A|$]]|$1|T|3|U|5|6|7|1H|8|@$R|1I|S|1J|V|W]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]]]

The standard template library is part of the standard. So it should be available on all standard compliant compilers as long as you have an implementation of the standard allocator (more on this).

The standard template library is treated "specially" on the literature for historical reasons, C++ was "born" on 1983 but the first standard was not released until 1998. 

The STL first implementation was on 1983 too, but for ADA language. The first port to c++ was not finished until 1992 by HP.

On 1993 it was proposed to be included on the ANSI standard and accepted on 1994 after some modifications.

This makes the STL on the stdlib a fork of the original STL.

On the early days some people used STL only to refer to the original HP library, later maintained by SGI, while other people used STL to refer to the subset of containers on the stdlib.

The STL external behaviour should be "the same" for all implementations, but the memory packaging may vary from one implementation to another.

Today the original C++ STL is no longer maintained, and talking about
 the STL should refer to the stdlib containers, although the standard itself doesn't use the STL acronym.

Finally, the stdlib containers use the standard <a href="http://en.cppreference.com/w/cpp/memory/allocator" rel="nofollow noreferrer">allocator</a> for it's memory management. On Linux GCC it's provided by libstdc++, on embedded systems you need to provide an implementation for the standard allocator yourself as you don't have an OS managing the memory for you.

This also applies for other functions that rely on system calls. <code>std::cout</code> won't be available on a bare metal system unless you define an implementation for it.

blocks|key|524398|text|这是否意味着我可以依赖stl“始终可用”？|type|blockquote|depth|inlineStyleRanges|entityRanges|data|524399|是的，标准库是C%2B%2B语言的一部分。因此，它保证它将“始终可用”与任何C%2B%2B编译器。|unstyled|524400|我能依赖于STL的一致性吗？|524401|是的，当然。C%2B%2B标准库是聪明的头脑们的精力充沛的努力，他们为我们带来了痛苦，使我们不能时不时地重新发明轮子，或者不得不相信第三方库，因为它们最终可能会把你甩在后面。它尽可能由成员组成，并尽可能泛泛。|524402|STL的每个函数/方法都有相同的行为吗？或者C%2B%2B发行版、操作系统或编译器之间是否有任何更改？|524403|C%2B%2B标准库在C%2B%2B标准中进行了描述。因此，可以保证在符合C%2B%2B标准的编译器中，C%2B%2B标准库的功能获得相同的行为，即标准兼容行为。C%2B%2B发行版之间有一些更改(例如，附加功能)，但向后兼容性得到了保证。也就是说，用C%2B%2B98编写的代码仍然可以编译，现代的C%2B%2B编译器支持C%2B%2B17+(少数例外)。|offset|length|524404|我之所以这样问，是因为当你不知道某些陷阱的时候，其他库有时真的会很痛苦。|524405|通常，鼓励您尽可能使用C%2B%2B标准库，并避免提供与标准库相同功能的第三方库。这是由于许多原因，其中一些原因是：|524406|Readability：C%2B%2B标准库是C%2B%2B的通用语言。也就是说，使用标准库可以提高代码的可读性，并减少将维护代码的其他人的学习曲线。|ordered-list-item|style|BOLD|524407|稳定性：标准库非常稳定，使用它可以使代码库更加稳定。|524408|保证生命时间支持：只要C%2B%2B存在，标准库就会存在和维护。|524409|Interoperability：标准库是跨平台的。|524410|entityMap|0|LINK|mutability|MUTABLE|url|http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/n4618.pdf^0|0|0|0|0|0|7|5|0|0|0|0|0|B|0|0|3|0|0|8|0|0|G|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1C|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|1D|8|@]|9|@]|A|$]]|$1|G|3|H|5|D|7|1E|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1F|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|1G|8|@]|9|@$M|1H|N|1I|1|1J]]|A|$]]|$1|O|3|P|5|6|7|1K|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1L|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|1M|8|@$M|1N|N|1O|V|W]]|9|@]|A|$]]|$1|X|3|Y|5|U|7|1P|8|@$M|1Q|N|1R|V|W]]|9|@]|A|$]]|$1|Z|3|10|5|U|7|1S|8|@$M|1T|N|1U|V|W]]|9|@]|A|$]]|$1|11|3|12|5|U|7|1V|8|@$M|1W|N|1X|V|W]]|9|@]|A|$]]|$1|13|3|-4|5|D|7|1Y|8|@]|9|@]|A|$]]]|14|$15|$5|16|17|18|A|$19|1A]]]]

<blockquote>
 Does this mean I can rely on the stl to be "always available"?
</blockquote>

Yes, the standard library is part of the C++ language. Thus, it is guaranteed that it will "always be available" with any C++ compiler.

<blockquote>
 Can I rely on consistency for the STL? 
</blockquote>

Yes, definitely. C++ Standard Library is the distilled effort of brilliant minds that suffered for us in order us not to have every now and then reinvent the wheel or to have to trust third party libraries that in the end might stub you in the back. It is as consisted and as generic as possible. 

<blockquote>
 Does every function/method of the STL always behave the same way?
 Or are there any changes between C++ releases, operating systems or compilers?
</blockquote>

The C++ Standard Library is described in the <a href="http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/n4618.pdf" rel="nofollow noreferrer">C++ standard</a>. Thus, it is guaranteed that among C++ standard compliant compilers the C++ Standard Library's functionality attains identical behavior i.e., standard compliant behavior. There are changes between C++ releases (e.g., additional functionality) but backward compatibility is guaranteed. That is, code written in C++98 is still compilable with modern C++ compilers supporting C++17 (with a small number of exceptions).

<blockquote>
 I ask this because other libraries can really be a pain sometimes, when you do not know about certain pitfalls.
</blockquote>

Generally, it is encouraged to use the C++ Standard Library where ever you can and to avoid third party libraries that offer the same functionality as Standard library offers. This is due to many reasons some of them are:

<ol>
<li>Readability: C++ Standard library is the lingua franca of C++. That is, using the standard library you make your code more readable and you reduce the learning curve for others that are going to maintain your code.</li>
<li>Stability: The standard library is extremely stable, using it you make your codebase more stable.</li>
<li>Guaranteed life time support: Standard library will exist and maintained as long C++ exists.</li>
<li>Interoperability: Standard Library is cross platform.</li>
</ol>

blocks|key|524429|text|几乎所有的C%2B%2B编译器都将附带标准C%2B%2B库。这些被称为“托管实现”。库定义得很好，虽然它确实在增长，但很少会以破坏旧代码的方式进行更改。标准委员会的一个主要目标是保持向后兼容性。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|524430|该标准还允许“独立实现”，它附带了一个非常精简的库，完全在标头中实现。在为嵌入式系统开发代码时，您可能会遇到这种情况，特别是当该系统没有底层操作系统时。这些是罕见的，但它们确实存在。(第7.6.1.13节讨论了独立实现。)|524431|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Nearly all C++ compilers will come with the Standard C++ library. These are called "hosted implementations." The library is well defined, and, while it does grow, it rarely changes in ways that would break older code. It's a major goal of the standards committee to maintain backwards compatibility.

The standard also allows for "freestanding implementations," which come with a very stripped-down library that's implemented entirely in the headers. You might encounter this when developing code for an embedded system, especially if that system doesn't have an underlying operating system. These are rare, but they do exist. (Section 7.6.1.13 talks about freestanding implementations.)

As a C++ beginner-level programmer I noticed no matter what IDE/compiler you use, you never need to explicitly include stl (Standard Template Library). Does this mean I can rely on the stl to be "always available"?

I mean if I want to use <code>std::cout</code> for example, I just include the <code>iostream</code> part of the stl:

<pre><code>#include &lt;iostream&gt;
</code></pre>

...and do not need to do something like <code>#include &lt;std&gt;</code> in the first place to continue with something like:

<pre><code>std::cout &lt;&lt; "Hello world!" &lt;&lt; std::endl;
</code></pre>

Furthermore: can I rely on consistency for the stl? Does every function/method of the stl always behave the same way? Or are there any changes between C++ releases, operating systems or compilers?

I ask this because other libraries can really be a pain sometimes, when you do not know about certain pitfalls. For example Eigen (for linear algebra stuff) was really hard for me to get it going and I noticed changing behavior between some releases...

C++: is std "magically" there? always?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

作为一个C++初级程序员，我注意到无论您使用什么IDE/编译器，您都不需要显式地包含stl (标准模板库)。这是否意味着我可以依赖stl“始终可用”？例如，如果我想使用std::cout，我只包含stl的iostream部分：#include <iostream>...and不需要首先执行类似#include <std...

问C++：性病“神奇地”存在吗？一直都是？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问C++：性病“神奇地”存在吗？一直都是？EN