blocks|key|778346|text|std::string或std::wstring，取决于您的需要。为什么？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|778347|它们是可移植的可移植代码它们可以处理standard|778348|They're+|unordered-list-item|778349|
|778350|它们有性能保证(根据针对缓冲区溢出和类似攻击的代码，|778351|778352|很容易根据需要转换为其他类型<|778353|
>H113>被很好地模板化，在减少代码膨胀和提高性能的同时为您提供了广泛的选择。真的。不能处理模板的编译器现在早就不存在了。|778354|C风格的字符数组是在自找麻烦。有时您仍然需要处理它们(这就是std::string.c_str()的用途)，但是，老实说，C中最大的危险之一是程序员使用char*做坏事并最终导致缓冲区溢出。不要这样做。|778355|wchar__t数组也是一样的，只是更大一些。|778356|CString、BSTR和CComBSTR不是标准的，也不能移植。除非绝对强制，否则请避免使用它们。最好是在需要时将std::string/std::wstring转换为它们，这应该不是很昂贵。|778357|注意，std::string只是std::basic_string的子类，但是除非您有充分的理由不使用std::string，否则最好还是使用std：：string。真的很棒。在这种情况下，让编译器来处理优化。|778358|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|12|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|13|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|14|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|16|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|17|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|18|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|19|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1A|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Y|$]]

std::string or std::wstring, depending on your needs. Why?

<ul>
<li>They're standard</li>
<li>They're portable</li>
<li>They can handle I18N</li>
<li>They have performance guarantees (as per the standard)</li>
<li>Protected against buffer overflows and similar attacks</li>
<li>Are easily converted to other types as needed</li>
<li>Are nicely templated, giving you a wide variety of options while reducing code bloat and improving performance. Really. Compilers that can't handle templates are long gone now.</li>
</ul>

A C-style array of chars is just asking for trouble. You'll still need to deal with them on occasion (and that's what std::string.c_str() is for), but, honestly -- one of the biggest dangers in C is programmers doing Bad Things with char* and winding up with buffer overflows. Just don't do it.

An array of wchar__t is the same thing, just bigger.

CString, BSTR, and CComBSTR are not standard and not portable. Avoid them unless absolutely forced. Optimally, just convert a std::string/std::wstring to them when needed, which shouldn't be very expensive.

Note that std::string is just a child of std::basic_string, but you're still better off using std::string unless you have a really good reason not to. Really Good. Let the compiler take care of the optimization in this situation.

blocks|key|3044230|text|std::string+!！|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3044231|这就是为什么他们称之为“标准”的原因。|3044232|basic_string是一个实现细节，应该忽略它。|3044233|BSTR+&+CComBSTR仅适用于带有COM的interop，并且仅适用于互操作的瞬间。|3044234|entityMap^0|0|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|S|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|M|$]]

std::string !!

There's a reason why they call it a "Standard".

basic_string is an implementation detail and should be ignored.

BSTR &amp; CComBSTR only for interOp with COM, and only for the moment of interop.

blocks|key|3044102|text|std::string，除非我需要调用专门接受您列出的其他参数之一的API。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3044103|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

std::string unless I need to call an API that specifically takes one of the others that you listed.

blocks|key|3889935|text|这篇文章比较了C%2B%2B中最常见的字符串类型，以及如何在它们之间进行转换。Unraveling+Strings+in+Visual+C%2B%2B|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3889936|entityMap|0|LINK|mutability|MUTABLE|url|http://www.johndcook.com/cplusplus_strings.html^0|Z|W|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Here's an article comparing the most common kinds of strings in C++ and how to convert between them. <a href="http://www.johndcook.com/cplusplus_strings.html" rel="nofollow noreferrer">Unraveling Strings in Visual C++</a>

blocks|key|3889260|text|如果可以使用MFC，请使用CString。否则，请使用std::string。另外，std::string可以在任何支持标准C%2B%2B的平台上工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3889261|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you can use MFC, use CString. Otherwise use std::string. Plus, std::string works on any platform that supports standard C++.

blocks|key|3889731|text|当我有选择的时候(我通常不会)，我倾向于使用带有UTF-8编码的std::string+(在UTF8+CPP库的帮助下)。我并不是很喜欢std::string，但至少它是标准的和可移植的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3889732|不幸的是，在我工作过的几乎所有实际项目中，都有内部string类-大多数实际上比std::string更好，但仍然...|3889733|entityMap|0|LINK|mutability|MUTABLE|url|http://utfcpp.sourceforge.net/^0|1A|8|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

When I have a choice (I usually don't), I tend to use std::string with UTF-8 encoding (and the help of <a href="http://utfcpp.sourceforge.net/" rel="nofollow noreferrer">UTF8 CPP</a> library. Not that I like std::string that much, but at least it is standard and portable.

Unfortunatelly, in almost all real-life projects I've worked on, there have been internal string classes - most of them actually better than std::string, but still...

blocks|key|3889913|text|我是一个Qt开发人员，所以我当然倾向于尽可能地使用QString+:)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3889914|它相当不错:兼容unicode，线程安全的隐式共享(也称为写入时复制)，并且它附带了一个API，旨在解决实际的实际问题(拆分、连接、替换(使用和不使用正则表达式)、数字之间的转换……)|3889915|如果我不能使用QString，那么就使用std::wstring。如果你坚持使用C，我推荐glib+GString。|3889916|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I am a Qt dev, so of course I tend to use QString whenever possible :).

It's quite nice: unicode compliant, thread-safe implicit-sharing (aka copy-on-write), and it comes with an API designed to solve practical real-world problems (split, join, replace (with and without regex), conversion to/from numbers...)

If I can't use QString, then std::wstring. If you are stuck with C, I recommend glib GString.

blocks|key|5300033|text|C风格的字符数组有自己的位置，但如果你广泛使用它们，你就会因为一个错误而浪费时间进行调试。我们有自己的string类，专门为(嵌入式开发环境)量身定做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5300034|我们不使用std::string，因为它并不总是对我们可用。|5300035|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|$]]

C-style char arrays have their place, but if you use them extensively you are asking to waste time debugging off by one errors. We have our own string class tailored for use in our (embedded development environment).

We don't use std::string because it isn't always available for us.

blocks|key|778241|text|只要有可能，我就会使用std::string+(或basic_string<TCHAR>)。它非常通用(就像CStringT一样)，它是类型安全的(不像printf)，并且它可以在每个平台上使用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|778242|entityMap^0|B|B|P|J|1I|8|24|6|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

I use <code>std::string</code> (or <code>basic_string&lt;TCHAR&gt;</code>) whenever I can. It's quite versatile (just like <code>CStringT</code>), it's type-safe (unlike <code>printf</code>), and it's available on every platform.

blocks|key|3044363|text|其他，std::wstring。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3044364|std::string是20世纪的技术。使用Unicode，销售给60亿人，而不是3亿人。|3044365|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|$]]

Other, std::wstring.

std::string is 20th century technology. Use Unicode, and sell to 6 billion people instead of 300 milion.

blocks|key|5300802|text|如果您使用的是MFC，请使用CString。除此之外，我完全同意其他大多数方法，std::string或std::wstring。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5300803|微软本可以通过在其最新的MFC更新中添加std::basic_string重载来给世界带来巨大的帮助。|5300804|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|$]]

If you're using MFC, use CString. Otherwise I agree with most of the others, std::string or std::wstring all the way.

Microsoft could have done the world a huge favor by adding std::basic_string&lt;TCHAR> overloads in their latest update of MFC.

blocks|key|3044427|text|我喜欢使用TCHAR，它是根据项目设置为wchar或char定义的。它在tchar.h中定义，您可以在其中找到所需函数和类型的所有相关定义。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3044428|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I like to use TCHAR which is a define for wchar or char according to the projects settings.
It's defined in tchar.h where you can find all of the related definitions for functions and types you need.

blocks|key|3044483|text|std::string和std::wstring，如果可以，还有其他东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3044484|它们可能不是完美的，但它们经过了良好的测试，很好地理解，并且非常通用。它们与标准库的其余部分配合得很好，这也是一个巨大的奖励。|3044485|同样值得一提的是，stringstreams。|offset|length|3044486|entityMap|0|LINK|mutability|MUTABLE|url|http://www.cppreference.com/wiki/io/sstream/start^0|0|0|9|D|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

std::string and std::wstring if I can, and something else if I have to.

They may not be perfect, but they are well tested, well understood, and very versatile. They play nicely with the rest of the standard library which is also a huge bonus.

Also worth mentioning, <a href="http://www.cppreference.com/wiki/io/sstream/start" rel="nofollow noreferrer">stringstreams</a>.

blocks|key|5300494|text|Unicode就是未来。不要使用char*和std::string。请)我已经厌倦了本地化错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5300495|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Unicode is the future. Do not use char* and std::string. Please )
I am tired of localization bugs.

blocks|key|3044620|text|string总比什么都没有好，但令人恼火的是，它缺少基本的功能，如拆分、连接，甚至是一个像样的格式调用……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3044621|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

std::string is better than nothing, but it's annoying that it's missing basic functionality like split, join and even a decent format call...

Which is your favorite way to go with strings in C++? A C-style array of <code>char</code>s? Or <code>wchar_t</code>? <code>CString</code>, <code>std::basic_string</code>, <code>std::string</code>, <code>BSTR</code> or <code>CComBSTR</code>?

Certainly each of these has its own area of application, but anyway, which is your favorite and why?

How do you handle strings in C++?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

在C++中，你最喜欢的字符串处理方式是什么？一个C风格的char数组？或wchar_t？CString、std::basic_string、std::string、BSTR或CComBSTR当然，其中每一个都有自己的应用领域，但不管怎样，哪一个是你最喜欢的，为什么？

问如何在C++中处理字符串？
EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在C++中处理字符串？EN

回答 15

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在C++中处理字符串？
EN