blocks|key|1091457|text|我见过许多C%2B%2B程序员在C#中编写COM风格的代码，试图解决该语言的不足之处。C#为你的枚举提供了很多类型安全的支持，而且通常有更好的API，然后P/Invoking回到C%2B%2B。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091458|我看到的另一件事是大多数人都注意到C#泛型不是模板。|1091459|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|$]]

I've seen many C++ coders code in a COM style in C#, trying to deal with the inadequacies of the language. C# provides lots of a type safe support for your enums and there are usually nicer APIs then P/Invoking back down to C++.

The other thing I've seen catch most people out is that C# generics are not templates.

blocks|key|1306555|text|调用GC.Collect。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1306556|entityMap^0|2|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

blocks|key|1091532|text|混淆“通过引用传递”和“引用类型”：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091533|void+GetAnArray(int+input,+ref+string[]+output);|code-block|syntax|javascript|1091534|(请比较C%2B%2B：void+getAnArray(int+input,+std::vector<std::string>&+output);)|offset|length|style|CODE|1091535|entityMap^0|0|0|8|1P|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Confusing "pass by reference" and "reference type":

<pre><code>void GetAnArray(int input, ref string[] output);
</code></pre>

(Compare with C++: <code>void getAnArray(int input, std::vector&lt;std::string&gt;&amp; output);</code>)

blocks|key|1091569|text|每次写入完整的命名空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091570|当您键入std::this或boost::that时，这在C%2B%2B中很好用。当你到处重复System.Windows.Forms.Whatever时，在C#中就不太好用了。|offset|length|style|CODE|1091571|entityMap^0|0|4|9|E|B|17|T|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|I|$]]

Writing the full namespace each time.

This is fine in C++ when you're typing <code>std::this</code> or <code>boost::that</code>. Not so great in C# when you repeat <code>System.Windows.Forms.Whatever</code> all over the place.

blocks|key|1091679|text|顺便说一句，C#编译器中有许多启发式方法，可以帮助经验丰富的C%2B%2B程序员解决C#程序员新手的问题。例如，如果你说|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091680|int+x[];|code-block|syntax|javascript|1091681|编译器会很有帮助地指出[]是C#中类型的一部分，所以您的意思可能是|1091682|int[]+x;|1091683|C#还允许将不必要的分号放在类声明的末尾，这样有这种习惯的C%2B%2B程序员就不会被它咬到。|1091684|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Incidentally, the C# compiler has a number of heuristics in it for helping out the experienced C++ programmer who is a novice C# programmer. For example, if you say

<pre><code>int x[];
</code></pre>

the compiler will helpfully point out that the [] is a part of the type in C#, so you probably meant

<pre><code>int[] x;
</code></pre>

C# also allows things like putting unnecessary semicolons at the end of a class declaration so that C++ programmers who are in that habit don't get bitten by it.

blocks|key|1091639|text|忘记为每个类成员指定访问修饰符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091640|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|$]]

Forgetting to specify access modifiers for every class member.

blocks|key|1306646|text|正在尝试在string%25s上实现const正确性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1306647|entityMap^0|5|6|G|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Attempting to implement <code>const</code> correctness on <code>string</code>s.

blocks|key|1091724|text|一个让我抓狂的地方，我相信很多非C%2B%2B的人也是，由于注册事件保持对象存活而导致的内存泄漏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091725|IDisposable一开始就很恼火(如果我说实话，现在仍然是这样)，但很明显，从本机代码到托管代码会有很大的不同，所以我不希望C%2B%2B开发人员真的会遇到这种情况，他们只是不喜欢它。|1091726|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|$]]

One that got me, and I believe a lot of non C++ people too, was leaking memory due to registered events keeping an object alive.

IDisposable grated to begin with (and still does if I'm honest) but was pretty obviously going to be a difference when going from native to managed code so it is not something I'd expect C++ developers to actually fall foul of, they just won't like it.

blocks|key|1091600|text|使用匈牙利符号和其他C%2B%2B命名约定|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091601|private+int+m_iMyIntField;
class+CWidget+{+...+}|code-block|syntax|javascript|1091602|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

using Hungarian Notation and other C++ naming conventions

<pre><code>private int m_iMyIntField;
class CWidget { ... }
</code></pre>

What are the most common or vicious mistakes when experienced C++ programmers develop in C#?

Most common or vicious mistakes in C# development for experienced C++ programmers

编译器

Windows

当有经验的C++程序员在C#中开发时，最常见或最严重的错误是什么？

问对于有经验的C++程序员来说，C#开发中最常见或最严重的错误
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于有经验的C++程序员来说，C#开发中最常见或最严重的错误EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对于有经验的C++程序员来说，C#开发中最常见或最严重的错误
EN