C:

Lack of distinction between function pointers (executable) and data pointers (you really don't want to execute this). Extreme unreadability. Making code look like it does what it does is orders of magnitude more difficult than making it do the task in the first place. Lack of clear support for lisp-think. Doing functional things is possible, barely, but it's not clear. Serious inconsistency between libraries about how error codes are returned. Antiquated string handling. The strings aren't strings, they're null-terminated blobs. This is all manner of wince-worthy.

Lisp:

()需要按shift键。每次我口齿不清的时候，我就把它和[]交换。

再给c++投一票…仍然是我最喜欢的语言，有几个亲密的追随者——C和Python。以下是我目前最讨厌的名单，排名不分先后:

Plethora of integer types inherited from C - way too many problems caused by signed vs. unsigned mistakes Copy constructors and assignment operators - why can't the compiler create one from the other automatically? Variable argument madness - va_list just doesn't work with objects and I'm so sick of problems created with sprintf(), snprintf(), vsnprintf(), and all of their relatives. Template implementation is required to be fully visible at compile time - I'm thinking of the lack of "export" implementations or at least usable ones Lack of support for properties - I want to have a read-only member like "a.x" that can be read publicly and only assigned internally. I really hate the "val=obj.getX()" and "obj.setX(val)". I really want properties with access control and a consistent syntax.

我可以为Python添加另一个:

给定一个列表l = [l1, l2，…]， ln]，那么repr(l) = [repr(l1)， repr(l2)，…， repr(ln)]，但str(l) != [str(l1)， str(l2)，…， str(ln)] (str(l) = repr(l))。之所以这样做，是因为列表中可能有模糊的条目，如l = ["foo]， [bar，"， "]，["]， str(l)将返回"[foo]， [bar，]，[]"，这“可能会使用户感到困惑”。然而，这使得str不可能仅用于转储数据，因为list杀死了“仅以可读格式转储数据”。Augh !

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

Javascript;

the dynamic binding of "this" is very confusing and dangerous if you don't know exactly what you're doing. a function declaration requires the keyword "function". It's not the typing I object to, it's the reading it when I want to do something slightly clever. Hrm now I think of it maybe that's a plus. Discourages me from doing clever things. As a result of number 2, it's often less code (in terms of characters) to just copy/paste a code segment than to declare it as a function, if it's a fairly short idiom. This unfortunately promotes bad practice, especially in my own code. Javascript makes motions at being a functional language by having first class functions and closures, but there's no way to verify referential transparency in a function, at either runtime or compile time. Without this, some architectures become either risky or bulky. Its fantastically bad reputation, and thus my inability to say "I program in javascript" to anyone without being laughed at.

Common Lisp:

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