blocks|key|4128569|text|回答你问题的第一部分：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4128570|LPCSTR是指向常量字符串的指针(LP表示Long+Pointer)|offset|length|style|CODE|4128571|LPCTSTR是指向UNICODE字符串的指针(TCHAR是宽字符还是宽字符，取决于项目中是否定义了UNICODE)|4128572|LPTSTR是指向(非常数)+TCHAR字符串的指针|4128573|在实践中，在过去讨论这些时，为了简单起见，我们省略了“指向a的指针”这一短语，但正如lightness-races+In+-orbit所提到的，它们都是指针。|4128574|这是一个描述C%2B%2B字符串的很棒的codeproject+article+(请参阅2/3向下的方式来比较不同类型的图表)|4128575|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2315311/what-is-a-long-pointer|1|http://www.codeproject.com/KB/string/cppstringguide1.aspx^0|0|0|6|M|C|0|0|0|7|O|5|0|0|6|F|5|0|0|G|J|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@$D|13|E|14|1|15]]|A|$]]|$1|H|3|I|5|6|7|16|8|@$D|17|E|18|F|G]|$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1B|8|@$D|1C|E|1D|F|G]|$D|1E|E|1F|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|1G|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1H|8|@]|9|@$D|1I|E|1J|1|1K]]|A|$]]|$1|P|3|-4|5|6|7|1L|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W]]|X|$5|S|T|U|A|$V|Y]]]]

To answer the first part of your question:

<code>LPCSTR</code> is a pointer to a const string (LP means <a href="https://stackoverflow.com/questions/2315311/what-is-a-long-pointer">Long Pointer</a>)

<code>LPCTSTR</code> is a pointer to a <code>const TCHAR</code> string, (<code>TCHAR</code> being either a wide char or char depending on whether UNICODE is defined in your project)

<code>LPTSTR</code> is a pointer to a (non-const) <code>TCHAR</code> string

In practice when talking about these in the past, we've left out the "pointer to a" phrase for simplicity, but as mentioned by lightness-races-in-orbit they are all pointers.

This is a great <a href="http://www.codeproject.com/KB/string/cppstringguide1.aspx" rel="noreferrer">codeproject article</a> describing C++ strings (see 2/3 the way down for a chart comparing the different types)

blocks|key|61985|text|快速和肮脏：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|61986|LP+==+Long+Pointer.只需考虑指针或字符*|offset|length|style|CODE|BOLD|61987|C+=+Const，在这种情况下，我认为他们的意思是字符串是常量，而不是指针是常量。|61988|STR为string|61989|T用于宽字符或字符(TCHAR)，具体取决于编译选项。|61990|entityMap^0|0|0|2|6|1|B|1|0|0|1|4|1|0|0|3|4|6|0|0|1|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|H]|$D|W|E|X|F|H]]|9|@]|A|$]]|$1|I|3|J|5|6|7|Y|8|@$D|Z|E|10|F|G]|$D|11|E|12|F|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@$D|14|E|15|F|G]|$D|16|E|17|F|H]]|9|@]|A|$]]|$1|M|3|N|5|6|7|18|8|@$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|P|$]]

Quick and dirty:

<code>LP</code> == Long Pointer. Just think pointer or char*

<code>C</code> = Const, in this case, I think they mean the character string is a const, not the pointer being const. 

<code>STR</code> is string

the <code>T</code> is for a wide character or char (TCHAR) depending on compile options.

blocks|key|894174|text|补充约翰和蒂姆的答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|894175|除非是针对Win98进行编码，否则在应用程序中只应使用两种6%2B字符串类型|894176|894177|LPWSTR|unordered-list-item|offset|length|style|CODE|894178|LPCWSTR|894179|894180|其余的则是为了支持ANSI平台或双编译。这些在今天已经不像以前那么重要了。|894181|entityMap^0|0|0|0|0|6|0|0|7|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|V|8|@$H|W|I|X|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|Y|8|@$H|Z|I|10|J|K]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|R|$]]

Adding to John and Tim's answer.

Unless you are coding for Win98, there are only two of the 6+ string types you should be using in your application

<ul>
<li><code>LPWSTR</code></li>
<li><code>LPCWSTR</code></li>
</ul>

The rest are meant to support ANSI platforms or dual compilations. Those are not as relevant today as they used to be.

blocks|key|894206|text|要回答问题的第二部分，您需要做如下操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|894207|LV_DISPINFO+dispinfo;++
dispinfo.item.pszText+=+LPTSTR((LPCTSTR)string);|code-block|syntax|javascript|894208|因为MS的LVITEM结构有一个LPTSTR，即一个可变的T字符串指针，而不是LPCTSTR。你所做的是|offset|length|style|CODE|894209|1)将string+(猜测中的CString+)转换为LPCTSTR+(实际上意味着获取其字符缓冲区的地址作为只读指针)|894210|2)通过丢弃其const-ness将只读指针转换为可写指针。|894211|这取决于dispinfo是用来做什么的，您的ListView调用是否有可能最终尝试通过该pszText+写。如果是这样的话，这可能是一件非常糟糕的事情:毕竟，您得到了一个只读指针，然后决定将其视为可写指针:也许这是有原因的！|BOLD|894212|如果您正在使用的是CString，那么您可以选择使用string.GetBuffer()+--这会特意为您提供一个可写的LPTSTR。然后，如果字符串确实发生了更改，则必须记住调用ReleaseBuffer()。或者，您可以分配一个本地临时缓冲区并将字符串复制到其中。|894213|在99%25的情况下，这是不必要的，并且将LPCTSTR作为LPTSTR可以工作……但总有一天，当你最意想不到的时候...|894214|entityMap^0|0|0|5|6|G|6|13|7|0|3|6|F|7|R|7|0|7|5|0|4|8|M|8|18|7|1G|1|0|9|7|Q|I|1O|6|2I|F|0|J|7|S|6|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|10|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|11|8|@$I|12|J|13|K|L]|$I|14|J|15|K|L]|$I|16|J|17|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|18|8|@$I|19|J|1A|K|L]|$I|1B|J|1C|K|L]|$I|1D|J|1E|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1F|8|@$I|1G|J|1H|K|L]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1I|8|@$I|1J|J|1K|K|L]|$I|1L|J|1M|K|L]|$I|1N|J|1O|K|L]|$I|1P|J|1Q|K|S]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1R|8|@$I|1S|J|1T|K|L]|$I|1U|J|1V|K|L]|$I|1W|J|1X|K|L]|$I|1Y|J|1Z|K|L]]|9|@]|A|$]]|$1|V|3|W|5|6|7|20|8|@$I|21|J|22|K|L]|$I|23|J|24|K|L]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|25|8|@]|9|@]|A|$]]]|Y|$]]

To answer the second part of your question, you need to do things like

<pre><code>LV_DISPINFO dispinfo; 
dispinfo.item.pszText = LPTSTR((LPCTSTR)string);
</code></pre>

because MS's <code>LVITEM</code> struct has an <code>LPTSTR</code>, i.e. a mutable T-string pointer, not an <code>LPCTSTR</code>. What you are doing is

1) convert <code>string</code> (a <code>CString</code> at a guess) into an <code>LPCTSTR</code> (which in practise means getting the address of its character buffer as a read-only pointer)

2) convert that read-only pointer into a writeable pointer by casting away its <code>const</code>-ness.

It depends what <code>dispinfo</code> is used for whether or not there is a chance that your <code>ListView</code> call will end up trying to write through that <code>pszText</code>. If it does, this is a potentially very bad thing: after all you were given a read-only pointer and then decided to treat it as writeable: maybe there is a reason it was read-only!

If it is a <code>CString</code> you are working with you have the option to use <code>string.GetBuffer()</code> -- that deliberately gives you a writeable <code>LPTSTR</code>. You then have to remember to call <code>ReleaseBuffer()</code> if the string does get changed. Or you can allocate a local temporary buffer and copy the string into there.

99% of the time this will be unnecessary and treating the <code>LPCTSTR</code> as an <code>LPTSTR</code> will work... but one day, when you least expect it...

blocks|key|899419|text|对问题第二部分的简短回答是，CString类并没有提供直接的类型转换，你所做的是一种欺骗。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|899420|更长的答案如下：|899421|您可以将CString类型转换为LPCTSTR的原因是因为CString通过覆盖operator=提供了此功能。根据设计，它只提供到LPCTSTR指针的转换，所以字符串值不能用这个指针修改。|899422|换句话说，出于与上面相同的原因，它根本不提供重载operator=来将CString转换为LPSTR。他们不想允许以这种方式改变字符串值。|899423|因此，本质上，诀窍是使用运算符CString提供并获得以下内容：|899424|LPTSTR+lptstr+=+(LPCTSTR)+string;+//+CString+provide+this+operator+overload|code-block|syntax|javascript|899425|现在LPTSTR可以进一步类型转换为LPSTR+:)|899426|dispinfo.item.pszText+=+LPTSTR(+lpfzfd);+//+accomplish+the+cheat+:P|899427|从'CString‘获取LPTSTR的正确方法是这样(完整的示例)：|899428|CString+str+=+_T("Hello");
LPTSTR+lpstr+=+str.GetBuffer(str.GetAllocLength());
str.ReleaseBuffer();+//+you+must+call+this+function+if+you+change+the+string+above+with+the+pointer|899429|同样，因为GetBuffer()返回LPTSTR，所以现在您可以修改:)|899430|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/cpp/atl-mfc-shared/reference/csimplestringt-class?view=msvc-160#getbuffer^0|E|7|0|0|4|7|G|7|14|9|1U|7|0|O|9|Z|7|19|5|0|0|0|0|0|C|6|0|0|I|6|5|B|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1D|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|1U|8|@]|D|@]|E|$]]|$1|N|3|O|5|P|7|1V|8|@]|D|@]|E|$Q|R]]|$1|S|3|T|5|6|7|1W|8|@]|D|@]|E|$]]|$1|U|3|V|5|P|7|1X|8|@]|D|@]|E|$Q|R]]|$1|W|3|X|5|6|7|1Y|8|@$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|P|7|21|8|@]|D|@]|E|$Q|R]]|$1|10|3|11|5|6|7|22|8|@$9|23|A|24|B|C]]|D|@$9|25|A|26|1|27]]|E|$]]|$1|12|3|-4|5|6|7|28|8|@]|D|@]|E|$]]]|13|$14|$5|15|16|17|E|$18|19]]]]

The short answer to 2nd part of the question is simply that <code>CString</code> class doesn't provide a direct typecast conversion by design and what you are doing is kind of cheat.
A longer answer is the following:
The reason you can typcast <code>CString</code> to <code>LPCTSTR</code> is because CString provides this facility by overriding <code>operator=</code>. By design it provides conversion to only <code>LPCTSTR</code> pointer so the string value can't be modified with this pointer.
In other words, it simply doesn't provide an overload <code>operator=</code> to convert the <code>CString</code> into <code>LPSTR</code> for the same reason as above. They don't want to allow altering the string value this way.
So essentially, the trick is to use the operator CString provide and get this:
<pre><code>LPTSTR lptstr = (LPCTSTR) string; // CString provide this operator overload
</code></pre>
Now LPTSTR can be further type casted to LPSTR :)
<pre><code>dispinfo.item.pszText = LPTSTR( lpfzfd); // accomplish the cheat :P
</code></pre>
The correct way to get <code>LPTSTR</code> from 'CString' is this though (complete example):
<pre><code>CString str = _T(&quot;Hello&quot;);
LPTSTR lpstr = str.GetBuffer(str.GetAllocLength());
str.ReleaseBuffer(); // you must call this function if you change the string above with the pointer
</code></pre>
Again because the <a href="https://docs.microsoft.com/en-us/cpp/atl-mfc-shared/reference/csimplestringt-class?view=msvc-160#getbuffer" rel="nofollow noreferrer">GetBuffer()</a> returns <code>LPTSTR</code> for that reason that now you can modify :)

What the difference between <code>LPCSTR</code>, <code>LPCTSTR</code> and <code>LPTSTR</code>?

Why do we need to do this to convert a string into a <code>LV</code> / <code>_ITEM</code> structure variable <code>pszText</code>: 

<pre><code>LV_DISPINFO dispinfo; 
dispinfo.item.pszText = LPTSTR((LPCTSTR)string);
</code></pre>

LPCSTR, LPCTSTR and LPTSTR

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

LPCSTR、LPCTSTR和LPTSTR之间的区别是什么为什么我们需要这样做才能将字符串转换为LV / _ITEM结构变量pszText：LV_DISPINFO dispinfo;  dispinfo.item.pszText = LPTSTR((LPCTSTR)string);

问LPCSTR、LPCTSTR和LPTSTR
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问LPCSTR、LPCTSTR和LPTSTREN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问LPCSTR、LPCTSTR和LPTSTR
EN