stop(); // Hammertime!

从Python / ceval.c:

/* This is gonna seem *real weird*, but if you put some other code between
   PyEval_EvalFrame() and PyEval_EvalCodeEx() you will need to adjust
   the test in the if statements in Misc/gdbinit (pystack and pystackv). */

//把这个放在这里的人是个白痴…这根本不管用!

但是代码还在那里……

顶部的:靠近单位顶部的:

// Oh what a tangled web we weave
// When first we practice to deceive
// ASTA

这一点对其他人来说很有趣，但对我来说就不那么有趣了。我从一个开发人员那里继承了代码(ASP)，而他自己也继承了它。第一个程序员编写了一些很难理解的代码。第二个开发者添加了如下评论(为了保护不那么无辜的人，名字被隐藏了):

'This code was written by **************.
'I haven't a clue what it does. He hasn't a clue what it does.
'Nobody else has a clue what it does or how it does it.
'It is something to do with data but **** knows what.
'The ******* still works so please do not change this code,
'even though it is a complete pile of ****.

那我为什么不觉得有趣呢?嗯，这是一个客户内部网的ASP代码。

.．.正是那位顾客向我强调了这条评论。

:-(

我们的团队，就在今晚，发布了一个新版本的CSS文件，删除了一个文件的注释，该文件的结构是这样的:

@charset "UTF-8";
/* Who knew comments here could COMPLETELY ruin our page in Safari? */
body {
        /* Really important stuff here */
        /* Of course, comment or not, this will all get ignored by Safari because 
           its the first rule after the comments which break everything.
           see http://www.w3.org/International/questions/qa-css-charset for the exact details!
        */
}

有趣的是，在网上你会发现人们的解决方案是输入一个虚假的元素作为字符集语句下面的第一条规则，然后被忽略，照常进行…

发人深省的问题:该把不评论的评论放在哪里?

旁注:我知道这是不需要的，因为头，元规则等。不幸的是，我们需要它作为一个catch all:(