blocks|key|1490371|text|把匈牙利语留给匈牙利人吧。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1490372|在这个例子中，我甚至省略了权威性的文章，只使用|1490373|private+const+int+Answer+=+42;|code-block|syntax|javascript|1490374|这就是答案，还是答案？|1490375|*使编辑作为Pascal严格正确，但我认为这个问题是寻求更多的life,+the+universe+and+everything的答案。|offset|length|1490376|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Life,_the_Universe_and_Everything^0|0|0|0|0|V|X|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Leave Hungarian to the Hungarians.

In the example I'd even leave out the definitive article and just go with 

<pre><code>private const int Answer = 42;
</code></pre>

Is that answer or is that the answer?

*Made edit as Pascal strictly correct, however I was thinking the question was seeking more of an answer to <a href="http://en.wikipedia.org/wiki/Life,_the_Universe_and_Everything" rel="noreferrer">life, the universe and everything</a>.

blocks|key|1490458|text|我相信ALL_CAPS是从C和C%2B%2B的工作方式中提取出来的。这篇here文章解释了风格差异是如何产生的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1490459|在新的集成开发环境(如Visual+Studio+)中，很容易识别类型、作用域以及它们是否是常量，因此它不是严格必要的。|1490460|FxCop和微软的StyleCop软件将为你提供指导，并检查你的代码，让每个人都能以同样的方式工作。|1490461|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/sourceanalysis/archive/2008/05/25/a-difference-of-style.aspx|1|http://en.wikipedia.org/wiki/FxCop|2|http://en.wikipedia.org/wiki/StyleCop^0|W|4|0|0|0|0|5|1|9|8|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

The ALL_CAPS is taken from the C and C++ way of working I believe. This article <a href="http://blogs.msdn.com/sourceanalysis/archive/2008/05/25/a-difference-of-style.aspx" rel="noreferrer">here</a> explains how the style differences came about.

In the new IDE's such as Visual Studio it is easy to identify the types, scope and if they are constant so it is not strictly necessary. 

The <a href="http://en.wikipedia.org/wiki/FxCop" rel="noreferrer">FxCop</a> and Microsoft <a href="http://en.wikipedia.org/wiki/StyleCop" rel="noreferrer">StyleCop</a> software will help give you guidelines and check your code so everyone works the same way.

blocks|key|1490510|text|实际上，它是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1490511|private+const+int+TheAnswer+=+42;|code-block|syntax|javascript|1490512|至少如果您查看.NET库，它是决定命名约定的最佳方式-这样您的代码就不会看起来不合适。|1490513|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Actually, it is 

<pre><code>private const int TheAnswer = 42;
</code></pre>

At least if you look at the .NET library, which IMO is the best way to decide naming conventions - so your code doesn't look out of place.

blocks|key|1490584|text|实际上，我倾向于在这里使用PascalCase+--但出于习惯，我对UPPER_CASE感到内疚……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1490585|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 actually tend to prefer PascalCase here - but out of habit, I'm guilty of UPPER_CASE...

blocks|key|1490653|text|首先，匈牙利表示法是使用前缀来显示参数的数据类型或预期用途的做法。微软的命名约定对匈牙利符号http://en.wikipedia.org/wiki/Hungarian_notation+http://msdn.microsoft.com/en-us/library/ms229045.aspx说不|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1490654|这里不鼓励使用大写:+Pascal大小写是可接受的约定和尖叫大写。http://en.wikibooks.org/wiki/C_Sharp_Programming/Naming|1490655|微软还在此声明，如果与现有方案匹配，则可以使用大写字母。http://msdn.microsoft.com/en-us/library/x2dbyw72.aspx|1490656|这基本上总结了这一点。|1490657|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Hungarian_notation|1|http://msdn.microsoft.com/en-us/library/ms229045.aspx|2|http://en.wikibooks.org/wiki/C_Sharp_Programming/Naming|3|http://msdn.microsoft.com/en-us/library/x2dbyw72.aspx^0|1A|1B|0|2M|1H|1|0|X|1J|2|0|S|1H|3|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]|$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]|V|$5|M|N|O|C|$P|W]]]]

First, Hungarian Notation is the practice of using a prefix to display a parameter's data type or intended use.
Microsoft's naming conventions for says no to Hungarian Notation
<a href="http://en.wikipedia.org/wiki/Hungarian_notation" rel="noreferrer">http://en.wikipedia.org/wiki/Hungarian_notation</a>
<a href="http://msdn.microsoft.com/en-us/library/ms229045.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/ms229045.aspx</a>

Using UPPERCASE is not encouraged as stated here:
Pascal Case is the acceptable convention and SCREAMING CAPS.
<a href="http://en.wikibooks.org/wiki/C_Sharp_Programming/Naming" rel="noreferrer">http://en.wikibooks.org/wiki/C_Sharp_Programming/Naming</a> 

Microsoft also states here that UPPERCASE can be used if it is done to match the the existed scheme.
<a href="http://msdn.microsoft.com/en-us/library/x2dbyw72.aspx" rel="noreferrer">http://msdn.microsoft.com/en-us/library/x2dbyw72.aspx</a>

This pretty much sums it up.

<pre><code>private const int THE_ANSWER = 42;
</code></pre>

or

<pre><code>private const int theAnswer = 42;
</code></pre>

Personally I think with modern IDEs we should go with camelCase as ALL_CAPS looks strange. What do you think?

C# naming convention for constants?

集成开发环境

Visual Studio

private const int THE_ANSWER = 42;或private const int theAnswer = 42;就我个人而言，我认为对于现代IDE，我们应该使用camelCase，因为ALL_CAPS看起来很奇怪。你认为如何？

问常量的C#命名约定？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问常量的C#命名约定？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问常量的C#命名约定？
EN