blocks|key|186419|text|我真的认为你收养哪一个并不重要，只要每个人都同意。有时，这可能是很难的，因为它似乎有些风格不符合人民的口味。也就是说，它可以归结为争论用m_作为所有成员变量的前缀是否漂亮。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|186420|我使用和修改土木油标准已经有一段时间了，这些都是针对C%2B%2B的。在what-is-your-favorite-coding-guidelines-checklist线程上还有其他一些|186421|entityMap|0|LINK|mutability|MUTABLE|url|http://geosoft.no/development/cppstyle.html|1|https://stackoverflow.com/questions/409/what-is-your-favorite-coding-guidelines-checklist#139459^0|1W|2|0|6|3|0|W|1D|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@]|D|@$9|V|A|W|1|X]|$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

I really think it does not matter which one you adopt, as long as everyone goes along with it. Sometimes that can be hard as it seems that some styles don't agree with peoples tases. I.e. it comes down to arguing about whether prefixing all member variable with <code>m_</code> is pretty or not.

I have been using and modifying the <a href="http://geosoft.no/development/cppstyle.html" rel="nofollow noreferrer">Geosoft</a> standards for a while, these are for C++. There are some other at the <a href="https://stackoverflow.com/questions/409/what-is-your-favorite-coding-guidelines-checklist#139459">what-is-your-favorite-coding-guidelines-checklist</a> thread

blocks|key|186523|text|C%2B%2B编码标准:101个规则、准则和最佳实践+(C%2B%2B深度系列)由Herb和Alexandrescu著.|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|186524|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0321113586^0|0|M|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]]]]

<a href="https://rads.stackoverflow.com/amzn/click/com/0321113586" rel="noreferrer" rel="nofollow noreferrer">C++ Coding Standards: 101 Rules, Guidelines, and Best Practices</a> (C++ In-Depth Series) 
by Herb Sutter and, Andrei Alexandrescu.

blocks|key|186345|text|嗯奇怪的问题。只需选择大多数团队成员熟悉的标准。为你的团队做一些调查。不知道如何才能在这里有所帮助:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|186346|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|$]]

Hmm, strange question. Just choose standard which most of the team members are familiar with. Make some kind of poll for your team. Not sure how SO can help here :)

blocks|key|860141|text|高完整性C%2B%2B编码标准手册-版本2.4|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|860142|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codingstandard.com/HICPPCM/index.html^0|0|J|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]]]]

<a href="http://www.codingstandard.com/HICPPCM/index.html" rel="noreferrer">High Integrity C++ Coding Standard Manual - Version 2.4</a>

blocks|key|855733|text|试试这个，这是美国宇航局戈达德太空飞行中心使用的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|855734|http://software.gsfc.nasa.gov/AssetsApproved/PA2.4.1.3.pdf|offset|length|855735|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1M|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

Try this one, it's the one that NASA's Goddard space flight centre uses.

<a href="http://software.gsfc.nasa.gov/AssetsApproved/PA2.4.1.3.pdf" rel="nofollow noreferrer">http://software.gsfc.nasa.gov/AssetsApproved/PA2.4.1.3.pdf</a>

blocks|key|186463|text|我为一家主要的英国公司写了一份编码标准，并且非常清楚为什么我选择了某些东西，而不仅仅是让它成为一堆“你应该”的声明。(-：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|186464|作为一种快速的出路，我建议：|186465|Scott的有效C%2B%2B第3版(亚马逊链接)+-如果你能找到这本书的第一版，然后购买它的概述OO设计，这是从以后的版本中删除。)-：|unordered-list-item|offset|length|186466|Scott的“有效STL+(亚马逊链接)”--您必须使用STL才能有效地使用C%2B%2B。|186467|史蒂夫麦康奈尔的书代码完成2+(亚马逊链接)+-不是C%2B%2B的具体，但充满了伟大的洞察力。|186468|entityMap|0|LINK|mutability|MUTABLE|url|https://rads.stackoverflow.com/amzn/click/com/0201924889|1|https://rads.stackoverflow.com/amzn/click/com/0201749629|2|https://rads.stackoverflow.com/amzn/click/com/0735619670^0|0|0|F|5|0|0|E|5|1|0|G|5|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@$G|11|H|12|1|13]]|A|$]]|$1|I|3|J|5|F|7|14|8|@]|9|@$G|15|H|16|1|17]]|A|$]]|$1|K|3|L|5|F|7|18|8|@]|9|@$G|19|H|1A|1|1B]]|A|$]]|$1|M|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]|U|$5|P|Q|R|A|$S|V]]|W|$5|P|Q|R|A|$S|X]]]]

I've written a coding standard for a major British company and was very conscious of putting reasons why I selected certain things rather than just make it a bunch of "Thou shalt" pronouncements. (-:

As a quick way out, I'd suggest mandating:

<ul>
<li>Scott Meyers's Effective C++ 3rd Edition (<a href="https://rads.stackoverflow.com/amzn/click/com/0201924889" rel="nofollow noreferrer" rel="nofollow noreferrer">Amazon link</a>) - if you can find a copy of the 1st edition of this book then buy it for the overview of OO design which was removed from later editions. )-:</li>
<li>Scott Meyer's book Effective STL (<a href="https://rads.stackoverflow.com/amzn/click/com/0201749629" rel="nofollow noreferrer" rel="nofollow noreferrer">Amazon link</a>) - you must use STL to use C++ efficiently.</li>
<li>Steve McConnell's book Code Complete 2 (<a href="https://rads.stackoverflow.com/amzn/click/com/0735619670" rel="nofollow noreferrer" rel="nofollow noreferrer">Amazon link</a>) - not C++ specific but full of great insights.</li>
</ul>

blocks|key|860062|text|只有当编码标准帮助您编写代码时，它们才有意义。因此，他们只需要保持代码的一致性(也就是说，如果有人将m_作为变量成员，而有人没有，则可能需要更长的时间来摸索代码，而不是使用相同的样式)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|860063|这就是他们应该做的，所以只要拿起你现有的代码，确保你的团队代码符合相同的风格。|860064|我喜欢把它当成动画片。如果你成为“辛普森一家”的漫画家，你必须以官方的方式画眼睛，否则一切看起来都是裤子，但如果你去“家庭盖伊”，你就得把它们画得与众不同。两种方法都不是错的。|860065|太多的标准都是关于毫无意义的限制的，这些限制是由不为自己编写代码的人编写的(或者认为自己太好了，无法遵守这些限制)。其他人试图教你如何编码。在一个好的标准中也没有它的位置，这些只是使您更容易查看一些代码并了解它所做的事情。|860066|例如：我的标准包括命名目录的规则--您将始终将代码放在一个名为项目名称的目录中，所有二进制文件都在bin+subdir中，所有配置文件都位于同一个位置，以及一个changelog等等。但我保证，我永远不会在根目录中找到一个与其二进制文件不同的项目，在根目录中，我不知道对它做了哪些更改。简单的，简单的东西，会带来巨大的不同。|860067|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

Coding standards are only meaningful if they help you write code. So they just need to keep your code consistent (ie if someone puts m_ for variable members and someone doesn't, it can take longer to grok the code than if they all used the same style).

That's all they (should) do, so just pick up your existing code and make sure your team codes to the same style.

I like to think of it like cartoons. If you become a cartoonist on the Simpsons, you have to draw eyes in the official way or everything looks pants, but if you go to Family Guy, you have to draw them differently. Neither way is wrong.

Too many standards are about meaningless restrictions, written by people who don't code themselves (or consider themselves too good to keep to them). Others try to teach you how to code. Neither has its place in a good standard, those just make it easier for you to look at some code and understand what its doing.

eg. my standards include rules for naming directories - you will always have your code in a directory called the same name as the project, and all binaries go in the bin subdir, with all config files in the same place, and a changelog, etc. All simple stuff, but I guarantee I'll never find a project called something different with its binaries in the root directory where I don't know what changes were made to it. Simple, easy stuff that makes a huge difference.

blocks|key|186579|text|我同意Harald的观点，最重要的是让球队在规则上达成一致，而不仅仅是选择外界推荐的规则。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|186580|我个人的建议是阅读Steve的代码完成，第二版，它描述了(许多其他有用的东西)几种常见的编码标准，并提供了对每种标准的评论。这可能有助于您的团队建立自己的标准。|offset|length|186581|entityMap|0|LINK|mutability|MUTABLE|url|http://cc2e.com/^0|0|F|8|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

I agree with Harald Scheirich, it is most important to have the team agree on what the rules should be rather than just picking a set that has been recommended by outsiders.

My personal recommendation would be to read <a href="http://cc2e.com/" rel="nofollow noreferrer">Code Complete, 2nd Edition</a> by Steve McConnell which describes (among a whole lot of other useful stuff) several common coding standards and offers commentary on each. This might help your team in setting up your own standards.

blocks|key|1185791|text|洛克希德·马丁公司的JSF+C%2B%2B编码标准是一个有趣的读物，但它有点过分，除非你在一个bug可以杀死人的领域工作。从计算机伦理学的角度来看，这仍然是一个非常重要的例子，比如如何以安全和正确的方式编程，这是最重要的例子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1185792|对于通用的C%2B%2B编码，我个人推荐Herb的C%2B%2B编码标准.从一开始，它就强调什么不应该标准化(与风格或偏好有关的事情，而不是促进安全性、正确性和效率的实践)。这也是你列表中最简单的阅读方式之一，为每个标准提供了简短而简洁的论据，这样就可以轻松地向同事展示。|1185793|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|$]]

Lockheed Martin's JSF Air Vehicle C++ Coding Standards is an interesting read but it's a bit overkill unless you're working in fields where a bug can kill people. It's still a very important example to look at from a computer ethics standpoint about an example of how to program with safety and correctness being top priority.

For general-purpose C++ coding, I'd personally recommend C++ Coding Standards by Herb Sutter. From the very beginning, it emphasizes what not to standardize (things relating to style or preference rather than practices that promote safety, correctness, efficiency). It's also among the easiest reads in your list giving very brief but concise arguments for each standard, making it something easy to show your co-workers.

blocks|key|186606|text|Poco+C%2B%2B编码风格的Guide.pdf|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|186607|entityMap|0|LINK|mutability|MUTABLE|url|http://www.appinf.com/download/CppCodingStyleGuide.pdf^0|0|M|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]]]]

<a href="http://www.appinf.com/download/CppCodingStyleGuide.pdf" rel="nofollow noreferrer">Poco C++ Coding Style Guide.pdf</a>

blocks|key|1185933|text|苹果可可编码指南|type|unordered-list-item|depth|inlineStyleRanges|entityRanges|offset|length|data|1185934|GNU编码标准|1185935|贝尔实验室的推荐的C风格和编码标准|1185936|来自POSIX+/+ISO的保留名称|1185937|Facebook+HHVM编码公约|1185938|GeoSoft+C%2B%2B编程风格指南|1185939|LLVM编码标准|1185940|C风格与SunOS编码标准|1185941|unstyled|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/CodingGuidelines/CodingGuidelines.pdf|1|http://www.gnu.org/prep/standards/standards.html|2|http://www.maultech.com/chrislott/resources/cstyle/indhill-cstyle.pdf|3|http://www.gnu.org/software/libc/manual/html_node/Reserved-Names.html|4|https://github.com/facebook/hhvm/blob/master/hphp/doc/coding-conventions.md|5|http://geosoft.no/development/cppstyle.html|6|http://llvm.org/docs/CodingStandards.html|7|http://www.cis.upenn.edu/~lee/06cse480/data/cstyle.ms.pdf^0|2|6|0|0|0|7|1|0|6|B|2|0|0|I|3|0|9|8|4|0|0|H|5|0|0|8|6|0|0|D|7|0^^$0|@$1|2|3|4|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|D|3|E|5|6|7|1I|8|@]|9|@$A|1J|B|1K|1|1L]]|C|$]]|$1|F|3|G|5|6|7|1M|8|@]|9|@$A|1N|B|1O|1|1P]]|C|$]]|$1|H|3|I|5|6|7|1Q|8|@]|9|@$A|1R|B|1S|1|1T]]|C|$]]|$1|J|3|K|5|6|7|1U|8|@]|9|@$A|1V|B|1W|1|1X]]|C|$]]|$1|L|3|M|5|6|7|1Y|8|@]|9|@$A|1Z|B|20|1|21]]|C|$]]|$1|N|3|O|5|6|7|22|8|@]|9|@$A|23|B|24|1|25]]|C|$]]|$1|P|3|Q|5|6|7|26|8|@]|9|@$A|27|B|28|1|29]]|C|$]]|$1|R|3|-4|5|S|7|2A|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]|10|$5|V|W|X|C|$Y|11]]|12|$5|V|W|X|C|$Y|13]]|14|$5|V|W|X|C|$Y|15]]|16|$5|V|W|X|C|$Y|17]]|18|$5|V|W|X|C|$Y|19]]|1A|$5|V|W|X|C|$Y|1B]]|1C|$5|V|W|X|C|$Y|1D]]]]

<ul>
<li>Apple <a href="https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/CodingGuidelines/CodingGuidelines.pdf" rel="nofollow">Coding Guidelines for Cocoa</a></li>
<li><a href="http://www.gnu.org/prep/standards/standards.html" rel="nofollow">GNU Coding Standards</a></li>
<li>Bell Labs' <a href="http://www.maultech.com/chrislott/resources/cstyle/indhill-cstyle.pdf" rel="nofollow">Recommended C Style and Coding Standards</a></li>
<li><a href="http://www.gnu.org/software/libc/manual/html_node/Reserved-Names.html" rel="nofollow">reserved names from POSIX / ISO</a></li>
<li>Facebook <a href="https://github.com/facebook/hhvm/blob/master/hphp/doc/coding-conventions.md" rel="nofollow">HHVM Coding Conventions</a></li>
<li><a href="http://geosoft.no/development/cppstyle.html" rel="nofollow">GeoSoft C++ Programming Style Guidelines</a></li>
<li><a href="http://llvm.org/docs/CodingStandards.html" rel="nofollow">LLVM Coding Standards</a></li>
<li><a href="http://www.cis.upenn.edu/~lee/06cse480/data/cstyle.ms.pdf" rel="nofollow">C Style and Coding Standards for SunOS</a></li>
</ul>

The following have been proposed for an upcoming C++ project.

<ul>
<li>C++ Coding Standards, by Sutter and Alexandrescu</li>
<li>JSF Air Vehicle C++ coding standards</li>
<li>The Elements of C++ Style</li>
<li>Effective C++ 3rd Edition, by Scott Meyers</li>
</ul>

Are there other choices? Or is the list above what be should used on a C++ project?

Some related links

<ul>
<li><a href="https://stackoverflow.com/questions/145508/do-you-think-a-software-company-should-impose-developers-a-coding-style">Do you think a software company should impose developers a coding-style?</a></li>
<li><a href="https://stackoverflow.com/questions/66268/what-is-the-best-cc-coding-style-closed">https://stackoverflow.com/questions/66268/what-is-the-best-cc-coding-style-closed</a></li>
</ul>

Existing Standard Style and Coding standard documents 

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯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编辑器全新改版上线，欢迎大家体验!

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

社区新版编辑器体验调研

下面是为即将到来的C++项目提出的建议。C++编码标准，Sutter和Alexandrescu著JSF飞行器C++编码标准C++风格的元素有效C++第三版，斯科特·迈尔斯著还有别的选择吗？还是上面列出的清单应该在C++项目中使用？一些相关链接

问现有标准样式和编码标准文档
EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问现有标准样式和编码标准文档EN

回答 11

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问现有标准样式和编码标准文档
EN