计划

缺少静态类型 没有静态函数重载(由于上述原因)导致字段访问器的名称很长 没有统一的对象系统 有点慢 相对较小的社区

Python:

Too slow! list operations don't return the list, so you can't do list.append(4).append(5). (I mean a reference to the same list, not a copy). This is a minor gripe; it's only come up a few times. statements don't return values (if, print, while, for, etc). This is only a problem when dealing with lambdas. lambdas can only be one expression. There's no real need for this restriction, as they are equivalent to functions in every other way. What if I want a button press event which calls two functions? I'd need to create a named function to supply that functionality to an action listener, while doing "lambda: f1(); f2()" would not hurt. you can only put standard a-zA-Z_0-9 as names. Having functions like "true?" and "+" would be great. Of course, this could lead to terrible obfuscation, but I'm not saying we immediately rename all functions to "p@$%3". Which do you find clearer to read: "dec2bin" or "dec->bin"? ("store_results" or "storeResults") or "store-results"?

我讨厌c++的五个方面

联系时间。使用分布式构建，我可以在同一时间重新构建我们的整个项目，它需要我们的链接器运行。 没有防止内存操作重新排序的标准方法。使用写组合内存通常需要滥用volatile关键字。防止读重排序(在处理SIMD数学管道时通常是优化的关键)通常是通过在例程中间注入空ASM块来实现的。 多步宏来解决字符串化问题:

#define STR_LINE2(x) #x
#define STR_LINE(x)   STR_LINE2(x)
#define LINE_NUMBER STR_LINE(__LINE__)

做字符串操作通常是很痛苦的。 大量的非标准化printf变体(vsnprintf_s vs _vsnprintf_s)。

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)。

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个:)

数组部分选择不能给你所要求的。

[1]给出一个元素 A[1:2]给出一个元素，而不是[A [1]， A [2]] A[1:3]给出2个元素

我讨厌这样，但可能是因为我大部分时间都在Verilog上工作。