blocks|key|3256034|text|就个人而言，我不会给自己的类加上前缀。因为Qt有它自己的实现(字符串，列表...)知道你在使用什么是有帮助的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256035|正确的方法应该是使用名称空间。我认为Qt没有使用它们，因为它太老了。C%2B%2B最近发生了很大的变化。|3256036|一般来说，根据语法颜色调整命名约定不是一个好主意(即使我知道这只会让你对命名感到疑惑)。|3256037|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|$]]

Personnally, I wouldn't prefix my own classes. As Qt has its own implementation of lots of thing (string, list...) it helps to know what you're using.

The correct way would be to use namespaces. I think that Qt didn't use them because it's quite old. C++ changed a lot lately.

And generally, adapting your naming conventions according to syntax colouring is a bad idea (even if I understand that it only made you wonder about your nameming).

blocks|key|3042120|text|我不明白为什么你要在你自己的类上强制这样做。让Qt按照它的类命名约定做它想做的事情，而你可以做你自己的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3042121|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 can't see why you would want to enforce this on your own classes at all. Let Qt do what it wants to do with its class naming convention and you do your own.

blocks|key|307559|text|使用您自己的编码约定和标准，它不必与您正在使用的库匹配。我不认为Qt的制作者是在暗示你遵循他们的风格惯例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|307560|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|$]]

Use your own coding convention and standards, it doesn't have to match the library you're using. I don't think the makers of Qt are implying that you follow their style conventions.

blocks|key|3256099|text|我没有使用过Qt，但除非你真的在扩展Qt的某些部分，否则我会认为给你自己的类加上Qt前缀是一个非常糟糕的主意，特别是考虑到你在Qt+Creator中报告的(IMO)+perculiar行为。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3256100|将相关类与前缀组合在一起是很常见的，但现在这是一种相当过时的方法。一种更好的方法是使用名称空间-这样做的好处是允许使用简单的前缀无法提供的作用域。|3256101|如果您使用名称空间，请确保您的名称空间将您正在执行的操作与您正在编写的代码区分开来，例如，不要使用|3256102|Qt::MyClass+theClass;|code-block|syntax|javascript|3256103|使用|3256104|venemo::MyClass+theClass;|3256105|我相信你已经明白了。您可能还希望查看QtCreator，并将编辑器(或整个集成开发环境)换成在C%2B%2B代码中突出显示效果更好的工具。|3256106|entityMap^0|0|0|0|0|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|E|5|6|7|U|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

I've not used Qt, but unless you're actually extending parts of Qt I would think it's a very bad idea to prefix your own classes with Qt, particularly because of the (IMO) perculiar behaviour that you're reporting from Qt Creator.

It's quite common to group related classes together with prefixes but this is quite a dated approach now. A better way to do this is using namespaces - this has the benefit of allowing scoping which a simple prefix won't give you.

If you do use namespaces, make sure that your namespace distinguishes what you're doing from the code you're writing against, e.g don't use

<pre><code>Qt::MyClass theClass;
</code></pre>

use

<pre><code>venemo::MyClass theClass;
</code></pre>

I'm sure you get the picture. You might also want to look at QtCreator and swap out the editor (or the entire IDE) for something that does better highlighting on C++ code.

blocks|key|307609|text|如果你正在考虑给你的类加上前缀'Q‘，只是为了让Creator为你突出显示它们，那么你可能想要更新为Creators主分支。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|307610|Creator使用了“Q+hack”，因为一直查找所有内容的代价太高了。与此同时，C%2B%2B引擎得到了极大的改进，这些查找可以在不减慢UI的情况下完成，所以最近激活了对所有类型的突出显示。|307611|不幸的是，这一变化将不再适用于Qt+Creator+2.0，因此此时您需要使用快照或自己构建整个内容。|307612|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|$]]

If you are considering to prefix your classes with 'Q' only to get Creator to highlight them for you, then you might want to update to a Creators master branch.

Creator used "the Q hack" since it was just to expensive to look up everything all the time. In the meantime the C++ engine was improved dramatically and these lookups can be done without slowing down the UI, so highlighting for all kinds of types was activated recently.

Unfortunately this change will not make it into Qt Creator 2.0 anymore, so you need to use either snapshots or build the whole thing yourself at this time.

blocks|key|309670|text|好吧，这就是我要做的。我尝试过，但通常都会失败，但无论如何，这都是值得尝试的，让我的大部分代码不知道我使用的是什么UI框架。特别是对于自定义窗口小部件的绘制操作，如果我从WX切换到Qt，我希望它们稍后可以再次工作。因此，我有自己的device_context，它是我所需要的东西的抽象。然后我有一个特定于WX的device_context版本，它调用wxDC+draw并保存一个wxDC*。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|309671|当然，您会认识到这就是Bridge模式。|309672|那么我该怎么命名呢？好吧，没有理由命名为device_context+wx_device_context，因为我很可能是在和Qt交谈。我试着从我的代码中隐藏wx，记得吗？|309673|但!代表我的客户创建的特定于WX的子类被命名为wx_device_context，实际上驻留在专门为此目的而创建的wx命名空间包中。|309674|这对你有什么影响？好吧，如果你想将一个类命名为QSomething，那么你可能正在创建一个自定义的东西，或者其他与Qt相关的特定方式。您是否可以通过子类化来隐藏这一事实，从而提供一个UI库不可知的接口供客户端使用？你正在制作的小工具可以用这种方式制作吗？如果您曾经决定需要使用其他UI库，您是被卡住了，还是可以简单地覆盖一些基本结构，以便您的自定义小部件可以与新的库一起工作？|309675|关键是，您将类命名为QSomething的诱惑是一种“气味”--尽管这是一种常见且通常可以容忍的味道--您可能想要考虑它表明了什么，以及您可以对此做些什么。|309676|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

Well, here's what I do. I try, and generally fail but IMHO it's worth trying anyway, to keep most of my code from knowing what UI framework I'm using. For the drawing operations of custom widgets in particular, I want them to work again later if I switch from WX to say Qt. Thus I have my own device_context of sorts that is an abstraction of what I need. Then I have a WX specific version of device_context that makes wxDC draw calls and holds a wxDC*.

You'll recognize this as the Bridge Pattern of course.

So what do I name things? Well, there's zero reason to name device_context wx_device_context since I could very well be talking to Qt. I'm trying to HIDE wx from my code, remember?

BUT! The WX specific subclass that is created on behalf of my clients IS named wx_device_context and actually resides in a wx namespace pocket created just for such purposes.

How does this apply to you? Well, if you're tempted to name a class QSomething then you're probably creating a custom something or other that's related to Qt in a specific way. Can you hide that fact through subclassing, providing an interface that clients could use that is UI library agnostic? Can the widget you are making be made in such a manner? If you ever decided you need to use some other UI library are you stuck or can you simply override some basic structures so that your custom widgets work with the new library? 

The point is that your temptation to name a class QSomething is a "smell"--albeit one commonly found and generally tolerated--and you might want to consider what it indicates and what you can do, if anything, about it.

blocks|key|304663|text|至于名称空间和Qt，Qt确实使用了名称空间，只是不是万能的。Qt可以在许多系统上运行，但并不是所有系统都完全支持名称空间。虽然有Qt的当前版本，但这并不意味着它运行的所有系统也都更新了。考虑到目前使用Qt的代码量，转换所有内容将是一项巨大的任务；假设Qt运行的所有编译器/平台/系统都不需要绕过，就可以将所有内容移动到名称空间中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|304664|Qt不需要命名空间，它们有一个有效的命名方案。因为使用Qt而希望以Qt的方式命名类，就像因为使用Qt而希望将类放在Qt名称空间中一样。我同意诺亚的观点，想要这样做是一种“气味”，虽然普遍可以容忍，但仍然不是一个好的举动。有时模仿并不是最真诚的奉承形式。|304665|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|$]]

As to namespaces and Qt, Qt does indeed use namespaces, just not for everything. Qt runs on many systems, not all of which may have full support for namespaces. While there are current versions of Qt, that doesn't mean all the systems it runs on have updated as well. Given the amount of code out there using Qt as it stands, converting everything would be a massive undertaking; assuming all the compilers/platforms/systems Qt runs on didn't have to be worked around to move everything into namespaces. 

Qt doesn't need namespaces, they have a naming scheme that works. Wanting to name your classes the way Qt does because you are using Qt is like wanting to put your classes in a Qt namespace because you are using Qt. I agree with Noah that wanting to do that is a "smell", and though generally tolerated is still not a good move. Sometimes imitation is not the most sincere form of flattery.

When I first started working with Qt, it was extremely annoying that every class has a name beginning with 'Q', but now I've got used to it.

I'm using Qt Creator, and it highlights code quite well. 
However, it only highlights class names beginning with 'Q'. And it highlights everything beginning with 'Q' even if there is no such type. 
It doesn't highlight custom class names.

That makes me wonder, should I also begin all my class names with 'Q'? 
Or at least the reusable ones? 
(I mean, those that I put in a class library, or reuse in another app.)

I've seen several places where they named their classes this way. Is it a good thing?

I found <a href="http://doc.trolltech.com/qq/qq13-apis.html" rel="noreferrer">this page</a> about Qt's naming conventions, but it doesn't deal with this question.

Also, I don't understand why Qt doesn't use namespaces.

EDIT:

Big thank you to everyone who shared his thoughts with me.

EDIT 2:

It seems that the newer versions of Qt Creator now also highlight the class names not beginning with 'Q'. Nice!

Should the name of my classes begin with 'Q' in Qt?

当我第一次开始使用Qt时，每个类都有一个以“q”开头的名称，这让我非常恼火，但现在我已经习惯了。我使用的是Qt Creator，它很好地突出了代码。但是，它只突出显示以“q”开头的类名。它会突出显示所有以“q”开头的内容，即使没有这样的类型。它不会突出显示自定义类名。这让我想知道，我的所有类名都应该以'Q‘开头吗？或者至少是可重用的？(我的意思是，那些我放在一个类库中，或者在另一个应用程序中重用的

问我的类名应该以Qt中的'Q‘开头吗？
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我的类名应该以Qt中的'Q‘开头吗？EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我的类名应该以Qt中的'Q‘开头吗？
EN