//Do not continue reading if you dont want to die.

这个差点要了我的命。

aComment = 'this is not aComment' # this is aComment
class T(object):
    def f(this):
        this is not aComment

我参与的一个大型项目在自动构建中使用了StyleCop和FXCop，并使用规则来防止人们检入带有未注释字段、方法、属性等的代码。

有些人对必须添加“获取或设置全名”之类的注释到自记录属性(如FullName)感到非常恼火，以至于他们不得不努力编写一个宏来绕过这些规则。

宏为方法、属性等插入了XML摘要标记，其中一个单一的不显示Unicode字符作为标记内容，这将欺骗构建规则，同时对为了注释而盲目坚持的东西进行轻微打击……

.．.至少直到他们引入了另一条规则来检查注释中的Unicode字符。

这是一个旧的IOCCC获奖条目，我不得不下载整个获奖档案——一个巨大的1.4 M——和grep的几个短语，我记得错了才找到它。

从语法上看，这可能不是注释。或许是这样。我还没想明白。它肯定没有注释分隔符，但也没有字符串分隔符。

C="Lint says "argument Manual isn't used."  What's that
mean?";

没有价格来猜测棉绒的产量。

对于好奇的人来说，这个条目在这里。

/* Only break the connection if it actually exists. It is important to
 * check the timeslot saved in the SOURCE of the disconnect message. */

我写了这条评论，现在我不记得为什么它很重要了…

Re eating one's own dogfood: We have the same term in our workplace (granted, only because I introduced it). My code is peppered with comments that say "TODO" and indicate something that ought to be done eventually, but a comment saying "DOGFOOD" (both keywords are always at the beginning of the comment, in all caps) means something that must be done before this program can be used even internally. It's a handy thing to search for, as the word "dogfood" is never going to appear in a quoted string - if it does, I can always just say "dog-food" or something - so even a case-insensitive search will come up with the right results.

Regarding zeroing the accumulator: I've done exactly the same thing when programming an Intel 80x86 (I started on the 8086 and moved up from there into the modern Pentiums). XORing a register with itself is the quickest and tightest way to clear it. Using "MOV AX,0" requires three bytes (opcode and two bytes of literal 16-bit zero), whereas "XOR AX,AX" is only two; it's even more noticeable with the 386-and-higher extended registers, where "MOV EAX,0" requires five bytes (four bytes of 32-bit zero). My C/C++ compiler always zeroes registers this way, so I'd assume it's still the best way (although I haven't studied opcode timing tables in ages, and probably both XOR reg,reg and MOV reg,imm take one clock).