我讨厌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)。

JavaScript:

The Object prototype can be modified. Every single object in your program gets new properties, and something probably breaks. All objects are hash maps, but it's difficult to safely use them as such. In particular, if one of your keys happens to be __proto__, you're in trouble. No object closure at function reference time. In fact, no object closure at all -- instead, this is set whenever a function is called with object notation or the new operator. Results in much confusion, particularly when creating event callbacks, because this isn't set to what the programmer expects. Corollary: calling a function without object notation or the new operator results in this being set equal to the global object, resulting in much breakage. Addition operator overloaded to also perform string concatenation, despite the two operations being fundamentally different. Results in pain when a value you expect to be a number is in fact a string. == and != operators perform type coercion. Comparisons between different types involve a list of rules that no mortal can remember in full. This is mitigated by the existence of === and !== operators. Both null and undefined exist, with subtly different, yet redundant meanings. Why? Weird syntax for setting up prototype chains. parseInt(s) expects a C-style number, so treats values with leading zeroes as octal, etc. You can at least parseInt(s, 10) but the default behaviour is confusing. No block scope. Can declare the same variable more than once. Can use a variable without declaring it, in which case it's global and probably breaks your program. with { }. Really difficult to document with JavaDoc like tools.

Common Lisp

conditions aren't classes (since classes came later), even though their interface is almost identical some of the names are just weird, e.g., flet / labels (only difference: scope), and defvar / defparameter (only difference: behavior when already defined), or any of the bit-twiddling functions (dpb, ldb, etc.) packages are ... really hard to get right -- every time I think I understand them, they don't do what I want built-in data structures and functions aren't as generic as they could be (e.g., why can't I define my own hash function portably?) multiple namespaces for functions, variables, etc. (I'm not opposed to this in principle, but CL made it too complex; Norvig has said he can't tell from the spec but there appear to be at least 7 namespaces)

C++

模板的语法 钻石传承问题 现代语言所拥有的标准库过多/缺乏(尽管boost也很接近)。 iostream IOStreams周围使用的语法

Python

空格是有意义的(有时) 强调关键词 有限的线程支持(至少目前) 用self代替this 空格是有意义的(有时)

C(好吧，这不是我最喜欢的，但当时还没人做过。)

套接字库语法。 没有函数重载。 c风格的字符串。 缓冲区溢出。 神秘的语法。我不知道有多少次我查到像atoi这样的东西，拍着我的额头，然后大喊“当然!”

编辑:如果我使用更多的库代码(就像我用套接字做的那样，但那些特别糟糕)，我可能会想出更多的库代码，但我已经觉得我选择C语言是在作弊。许多语言的存在只是为了取C语言的好的部分，取代坏的部分，这有点像在徒劳无益。

PHP

几乎每个标准函数都在全局作用域中 不一致的函数参数顺序 不一致的函数命名 不区分大小写的函数 脚本的行为可能会因php.ini文件的不同而有所不同 能够使用未定义的变量 在某些情况下，必须将结果赋值给变量，然后才能在函数中使用它

更主观地说:

动态类型