Delphi(又名Object Pascal)，我将讨论本机版本，而不是。net。

Var块! 语言中的接口在设计时就考虑到了COM的使用——因此比c#或Java要复杂得多。ie。涉及引用计数，除非显式禁用它。 没有尝试，只有最终结束; 对象创建过于显式: var obj: TMyObject; .．. obj:= TMyObject.Create; 试一试 .．. 最后 obj.Free; 结束;

而是像这样

auto obj: TMyObject; // compiler adds the default constructor call and the destructor call in a try/finally block. 

好吧，语言太好了，我真的想不出更多，所以我在这里强迫自己:内置类型，如字符串，整数..或者枚举最好有方法。ie。i. tostring代替IntToStr(i)。

Lua

我喜欢这门语言，但是有一些事情困扰了我很多年!

No (built-in) support of binary operations (as of 5.1, it might come with 5.2). Should have a built-in binary buffer implementation, allowing for example in place long string concatenation. I know it doesn't fit well in the syntax, but sometime I miss longVariableName++ or verboseVariableName += 5. Reference assumes knowledge of C (I have it but it is a minus for newcomers) and defers some help to C reference! And sometime it is too terse. It is starting to have a good deal of libraries, but you have to get them from various places. On the other hand, the download is very small! ;-)

c#中缺少预处理器。

我知道他们把它放在一边是因为有些人会滥用它，但我认为他们把孩子和洗澡水一起倒掉了。代码生成被认为是一件好事，在c++中，预处理程序是我的第一个代码生成器。

Common Lisp:

关键词往往太啰嗦。 库支持是可怜的。 在希望更严格地处理内存的操作系统中不能很好地工作。 没有与操作系统交互的良好工具。 “循环”功能没有很好地定义，当然看起来也不像Lispy。

C++

The inconsistencies in the libraries related to char* and std::string. All C++ libs should take std::strings. Characters are not bytes with respect to iostream. I do a lot of byte-oriented work. Having a "byte" type and a "character" type would significantly make it simpler. That, too, would permit scaling to Unicode somewhat easier. Bit operations should be easy on a value. I should be able to access and set the n'th bit of a value without playing AND/OR dancing. The lack of a standardized interface for GUIs. This is where Microsoft has really been able to position themselves well with C#. A standard interface binding that OS makers provide would go really far for my work.

c# / .net:

Classes should be sealed by default There should be no lock statement - instead, you should have specific locking objects, and there should be methods such as Acquire which return disposable lock tokens. Corollary: there shouldn't be a monitor for every object. GetHashCode() and Equals() shouldn't be in System.Object - not everything's suitable for hashing. Instead, have an IdentityComparer which does the same thing, and keep the IComparer<T>, IComparable<T>, IEqualityComparer<T> and IEquatable<T> interfaces for custom comparisons. Poor support for immutability Poor way of discovering extension methods - it should be a much more conscious decision than just the fact that I'm using a namespace.

这些都是我想出来的，明天问我，我会想出一个不同的5个:)