你遇到过的源代码中最好的注释是什么?

小开

//ALL YOUR BASE ARE BELONG TO US

.．.这让我的老板以为有人黑进了系统。他不知道这个笑话。

小开

Get This hack!

在一行汇编代码中，在几页未注释的代码之后。

小开

我发现了这个:

I'm not sure what I did

小开

// TODO: Implement this function!

小开

//I am not sure why this works but it fixes the problem.

这是之前的一组代码，技术上确实解决了问题，它的意思是，但打破了其他3个东西....

小开

目前为止最好的一个:

"This code makes baby Jesus very sad!".

它像这样引用一个String的初始化:

String blankSpaces="&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "+ //100 whitespaces
"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "+ //200 Whitespaces
...
"                                        " //100 whitespaces

你懂的。

小开

/* Please work */

小开

下面是一个必须声明的局部变量，只是为了将一个常量传递给库函数:

// This only exists because Scott doesn't know how to use const correctly

小开

许多年前(大约1994年)，我为一家大型跨国软件公司开发Oracle PRO*C应用程序，您可能听说过这家公司。我正在开发的应用程序是一个大型的Oracle应用程序，他们有一个实用程序可以整夜运行，整理数据并进行各种汇总计算。每次需要作为批处理作业处理任何事情时，它都被推到这个实用程序中，您可以想象它变得非常可怕。同样值得注意的是，对于如此庞大的程序，它的评论数量很少。

它为数不多的评论之一仍然是我所见过的对纯粹的WTF的最好的评论……我试图在一个函数中找到一个bug，它有数百行长，中间是函数中的只有注释:

/* I did this the other way */

直到今天，这仍然是我所见过的最好的评论。

小开

/* You are not meant to understand this */

小开

//Code sanitized to protect the foolish.
using System;
using System.Collections.Generic;
using System.Text;
using System.Reflection;
using System.Web.UI;


namespace Mobile.Web.Control
{
/// <summary>
/// Class used to work around Richard being a fucking idiot
/// </summary>
/// <remarks>
/// The point of this is to work around his poor design so that paging will
/// work on a mobile control. The main problem is the BindCompany() method,
/// which he hoped would be able to do everything. I hope he dies.
/// </remarks>
public abstract class RichardIsAFuckingIdiotControl : MobileBaseControl, ICompanyProfileControl
{
protected abstract Pager Pager { get; }


public void BindCompany(int companyId) { }


public RichardIsAFuckingIdiotControl()
{
MakeSureNobodyAccidentallyGetsBittenByRichardsStupidity();
}


private void MakeSureNobodyAccidentallyGetsBittenByRichardsStupidity()
{
// Make sure nobody is actually using that fucking bindcompany method
MethodInfo m = this.GetType().GetMethod("BindCompany", BindingFlags.DeclaredOnly |
BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic);
if (m != null)
{
throw new RichardIsAFuckingIdiotException("No!! Don't use the fucking BindCompany method!!!");
}
// P.S. this method is a joke ... the rest of the class is fucking serious
}


/// <summary>
/// This returns true if this control is supposed to be doing anything
/// at all for this request. Richard thought it was a good idea to load
/// the entire website during every request and have things turn themselves
/// off. He also thought bandanas and aviator sunglasses were "fuckin'
/// gnarly, dude."
/// </summary>
protected bool IsThisTheRightPageImNotSureBecauseRichardIsDumb()
{
return Request.QueryString["Section"] == this.MenuItemKey;
}


protected override void OnLoad(EventArgs e)
{
if (IsThisTheRightPageImNotSureBecauseRichardIsDumb())
{
Page.LoadComplete += new EventHandler(Page_LoadComplete);
Pager.RowCount = GetRowCountBecauseRichardIsDumb();
}
base.OnLoad(e);
}


protected abstract int GetRowCountBecauseRichardIsDumb();
protected abstract void BindDataBecauseRichardIsDumb();


void Page_LoadComplete(object sender, EventArgs e)
{
BindDataBecauseRichardIsDumb();
}


// the rest of his reduh-ndant interface members
public abstract string MenuItemName { get; set; }
public abstract string MenuItemKey { get; set; }
public abstract bool IsCapable(CapabilityCheck checker, int companyId);
public abstract bool ShowInMenu { get; }
public virtual Control CreateHeaderControl()
{
return null;
}
}
}

更新:代码的原始作者已经暴露了自己，所以我必须给它应有的信用。丹·麦金利在我开始工作后不久离开了我所在的公司，他谈论了更多关于代码的内容，解释了一些背景知识和一些“Richard”写的“WTF’s”。

小开

Catch (Exception e) {
//who cares?
}

小开

我不止一次使用过这个方法，当我对一个数学公式做了一些不明显的简化时，我不想记录:

//this formula is right, work out the math yourself if you don't believe me

小开

// I'm sorry.

小开

在头文件的顶部:

/* Project : XYZ (Please somebody shoot me!)
*
* File : $Id: defs.h,v 1.1 $
*
* Purpose : Create havoc rather than peace among many nations
*
* History : Back-ported changes that were not in CVS.  Please somebody,
*  shoot us and put us all out of our misery.
*/

“XYZ项目”(已改名)是一个长达七年的折磨。最后这句话是由一个从头到尾都参与其中的坚定的灵魂写的。

小开

从USENET的经典:

在Teradyne硬件建模器代码的深处是一个例程一大堆十六进制数字到SYS$QIO调用中。唯一的评论是 “这里发生了奇怪的魔法”。

小开

// This code sucks.

小开

{
This is a gathering place for all unit tests.
Create a TUnitTestWrapper, then call "RunAllUnitTests".


This class will create an instance of each thing to be tested, and call each of
their unit tests.


It does not really do any testing on it's own; it just gives a common place from
which to call everyone else's tests.


This way, one day, we can automate our testing with each build. [Cue laughter]
}

小开

int Q13Factor = 8125; // 2^13 for Q13

小开

-- Comment this later

这是一个4000多行的PL/SQL过程的第2行。唯一的评论。手术已经进行了4年了，后来还是没来…

小开

在开发团队中每个人都在大量编辑的代码文件头部:

'Avert your eyes, it may take on other forms!

好弗兰德斯。

小开

//You are not expected to understand this

经典。

小开

在一个完全没有注释的2000行方法中

{
{
while (.. ){
if (..){
}
for (.. ){
}
.... (just putting in the control flow here, imagine another few hundred ifs)
if(..)   {
if(..)     {
if(..)   {
...
(another few hundred brackets)
}
}
} //endif

(实际上有一天，我把所有的括号都去掉了，只是为了看看它有多糟糕，而且，没有格式化，得到了这个:

\{\{\{\{}}{}{}{}{}}\{\{}\{\{}{}{}{}{}{}\{\{}{}}{}{}\{\{}{}{}{}{}{}{}{}{}{}{}\{\{}}}\{\{}\{\{}}\{\{{}}}\{\{}{}{}{}{}{}{}\{\{}}{}\{\{{}}{}\{\{}{}}\{\{{}}{}{}{}{}}\{\{}}}{}\{\{}{}{}\{\{}\{\{}}{}}\{\{}}}\{\{}}\{\{}}\{\{}}{}\{\{}}\{\{}}\{\{}}\{\{}{}{}}{}{}\{\{{}}\{\{}}}{}{}{}{}}\{\{{}\{\{}{}{}\{\{}{}{}{}{}{}}{}}\{\{}}\{\{}{}}}\{\{}}\{\{}}}\{\{}}\{\{}}{}{}{}{}\{\{}}\{\{}{}{}{}}}}{}{}}\{\{}\{\{{}{}{}{}}}}\{\{}\{\{{}}}}\{\{}\{\{{}\{\{}}{}\{\{}}{}\{\{}{}}\{\{}}{}\{\{}}}\{\{}}}}\{\{}{}{}{}{}\{\{{}    \{\{\{\{}}{}{}{}{}}\{\{}\{\{}{}{}{}{}{}\{\{}{}}{}{}\{\{}{}{}{}{}{}{}{}{}{}{}\{\{}}}\{\{}\{\{}}\{\{{}}}\{\{}{}{}{}{}{}{}\{\{}}{}\{\{{}}{}\{\{}{}}\{\{{}}{}{}{}{}}\{\{}}}{}\{\{}{}{}\{\{}\{\{}}{}}\{\{}}}\{\{}}\{\{}}\{\{}}{}\{\{}}\{\{}}\{\{}}\{\{}{}{}}{}{}\{\{{}}\{\{}}}{}{}{}{}}\{\{{}\{\{}{}{}\{\{}{}{}{}{}{}}{}}\{\{}}\{\{}{}}}\{\{}}\{\{}}}\{\{}}\{\{}}{}{}{}{}\{\{}}\{\{}{}{}{}}}}{}{}}\{\{}\{\{{}{}{}{}}}}\{\{}\{\{{}}}}\{\{}\{\{{}\{\{}}{}\{\{}}{}\{\{}{}}\{\{}}{}\{\{}}}\{\{}}}}\{\{}{}{}{}{}\{\{{}{}\{\{}}{}}}{}}\{\{}}\{\{}{}}\{\{}\{\{}\{\{}}}}\{\{{}\{\{{}}}}}\{\{\{\{{}}}}}{}{}{}\{\{\{\{}}}{}{}}\{\{}\{\{}}}}{}\{\{}}{}}}{}}\{\{}}\{\{}{}}\{\{}\{\{}\{\{}}}}\{\{{}\{\{{}}}}}\{\{\{\{{}}}}}{}{}{}\{\{\{\{}}}{}{}}\{\{}\{\{}}}}

endif出现在第800行左右)

小开

简单但有效的注释，在一些不太安全的c++代码之前

// yikes

小开

这实际上是我在实现原型转换为实际代码时所做的:

// Abandon all hope you who needs to debug this

是的，有比我聪明的人在之后重构了代码(它必须有一个好的结局)。

小开

THIS PROGRAM HAS CODE THAT DOES NOT MEET STANDARDS

这个评论几乎出现在我们这里的每一个节目中....

小开

这不是严格意义上的评论，但是…

那是20世纪90年代中期，我正在做一个大的迁移:一个小软件供应商，大客户端，压力很大。我们有很多转移门柱的东西;这个项目很难控制。我是关键的开发人员，但对系统还不熟悉，而另一个开发人员是供应商的所有者/创始人。

在几个月没有按时完成任务，也没有让客户满意之后，公司的所有者/创始人找来了另一名远程工作的开发人员。(我可以大胆地说，新开发人员的技能和经验都不如我。)

好吧，这个新人对我已经做过的代码做了一些更改，然后一两个月后我又回到了代码的同一区域，其中有一些我以前没有见过的变量。像StupidMark这样的名称。

伙计，这是不对的。我的意思是，有团队合作的考虑，但也:在这种环境下，变量名可以在运行时错误消息中显示。我只是说。

在我看来，那个新人的代码并没有让我们更接近可交付的产品，这让侮辱变得更伤人了。

小开

// If this comment is removed the program will blow up

小开

当被问及什么是“最好的评论”时，我们的回答都是我们能找到的最糟糕的评论，这充分说明了我们的职业……

小开

If you have reached this part in the code, then this program sucks.

小开

using namespace std;            // So sue me

小开

最初的《毁灭战士》拥有一个带有静态墙壁的引擎，但却不能移动;结果，所有的门都是垂直打开的;任何东西都不可能水平移动。当源代码发布后，我在查看代码时，在处理门的源文件中看到了这个，在一大块注释掉的代码的开头:

// UNUSED
// Separate into p_slidoor.c?


#if 0           // ABANDONED TO THE MISTS OF TIME!!!
//
// EV_SlidingDoor : slide a door horizontally
// (animate midtexture, then set noblocking line)
//

小开

// but the "real" solution is much more complicated

从jpgraph

小开

// this is really complicated

没有其他评论了

小开

// Magic. Do not touch.

小开

// Okay, let's do the loop, yeah come on baby let's do the loop
// and it goes like this ...

小开

大概30页的xslt的中间部分

<!-- Here be dragons  -->

小开

/* logic */
#ifndef TRUE
# define TRUE 1
#endif /* TRUE */
#ifndef FALSE
# define FALSE 0
#endif /* FALSE */
#define EOF_OK TRUE
#define EOF_NOT_OK FALSE

和mkentry.c的其余部分在IOCCC页。每次读这篇文章的时候，我都笑不出来。

小开

试着把你最喜欢的脏话输入谷歌代码搜索，它会消磨掉许多无聊的时间。以下是我最喜欢的例子:

/* These magic numbers are fucking stupid. */


/* Dear free software world, do you NOW see we are fucking
things up?! This is insane! */


/* We will NOT put a fucking timestamp in the header here. Every
time you put it back, I will come in and take it out again. */


# However, this only works if there are MULTIPLE checkboxes!
# The fucking JS DOM *changes* based on one or multiple boxes!?!?!
# Damn damn damn I hate the JavaScript DOM so damn much!!!!!!


/* TODO: this is obviously not right ... this whole fucking module
sucks anyway */


/* FIXME: please god, when will the hurting stop? Thus function is so
fucking broken it's not even funny. */

我个人最喜欢的

 # code below replaces code above - any problems?
# yeah, it doesn't fucking work.

小开

// drunk, fix later

真希望我是在开玩笑。根据编写代码的开发人员的了解，我认为他是认真的。

小开

// I have to find a better job

小开

以下是4个，排名不分先后:

// Father, forgive me, for I am sinning


// heaven help me


// horse string-length into correctitude
(from a textbook)


// what, me worry?

小开

“这永远不会发生”。

朋友，这是我的临终遗言……

小开

(A bunch of code that's really weird looking)  //Kludge.

小开

return 1; # returns 1

小开

//This code sucks, you know it and I know it.
//Move on and call me an idiot later.

小开

在向一个朋友展示这篇文章来自Coding Horror几个小时后，我看到他的代码上有这样的注释:

// valdez先生是一个暴力的精神病患者。别惹他生气。

小开

/* This is O(scary), but seems quick enough in practice. */

后面是四个嵌套的for循环

小开

// Bad Christian, No cookie

在这种情况下，Cookie 不指的是浏览器Cookie

小开

const int TEN=10; // As if the value of 10 will fluctuate...

小开

//The following code is commented out
//(a load of commented out code followed)

小开

我经历了一个睡眠不足的编程过程，开始只写引用自《搏击俱乐部》的评论。

多年后，我仍然在浏览代码，发现了一条让我发笑的评论。大多数只是随机的想法。然而，我确实保持我的评论行比率相当好!

// This shouldn't happen. The only way this can happen is if the
// <code>JFileChooser</code> has returned a <code>File</code> that doesn't exist
// on the system. If this happens we can't recover, and there is more than likely
// a rip in the space time continuum that the user is too distracted by to notice
// anything else.

 /**
* This method leverages collective synergy to drive "outside of the box"
* thinking and formulate key objectives into a win-win game plan with a
* quality-driven approach that focuses on empowering key players to drive-up
* their core competencies and increase expectations with an all-around
* initiative to drive down the bottom-line. I really wanted to work the word
* "mandrolic" in there, but that word always makes me want to punch myself in
* the face.
*/
private void updateFileCountLabel() {

小开

// sometimes I believe compiler ignores all my comments

小开

# absolutely foul heuristic code.
# ..it's dirty, but you want it.

和:

# VERY USEFUL DEBUGGING AID, for when the above all goes pearshaped:

小开

刚从大学毕业的我渴望亲自动手。我的第一个任务是……“为我注释此代码”。

傻瓜。

过了一段时间我就厌倦了……

// this function doesn't actually calculated the profit, like it says --it really signals the mothership orbiting saturn that the planet is ripe for takeover


[later]


// I don't think anyone is going to read this


[various permutations on that last one]

小开

/* Halley's comment */

小开

事实上，有一天我在一些代码上看到了这个，这些代码是在截止日期很急的时候写的。

//This was clearly written under duress

小开

经典ASP:

'Is it worth it, let me work it'
'I put my thing down, flip it and reverse it'
'Ti esrever dna ti pilf, nwod gniht ym tup I'


NextIP = StrReverse(UserRecordset.Fields.Item(0))

小开

我在重用我很久以前写的一个PHP类时发现了这一点。我仍然不记得那里有什么，我仍然发现它没有任何用处……我甚至不记得我写过那篇评论;所以当我找到它的时候，我真的笑出声来了。

try
{
// Some database logic
}
catch (Exception $ex)
{
// sure, it looks silly and I honestly cant remember what code used to go here... but i swear i will
// find a use for this code.... eventually....
throw $ex;
}

小开

'NO COMMENT

小开

其中最经典的是皮埃尔·德·费马对他著名的“大定理”所作的评论:“这一页的空白处太小了，无法写下证明。”

350多年后才找到证据。

(根据维基百科，这是原始文本:)

Cubum autem in duos cubos, aut 二重奏中的四边形四边形，等等泛化无限超四边形中的零在二人的提名中 Est divide ere cuius rei demonstrationem 神奇神智清醒。Hanc marginis

…并翻译成英语:

)不可能分离一个立方体化成两个立方，或者化成四次方 2 / 4次方，或者一般来说，任意幂大于二成二喜欢权力。我发现了一个真正的这是一个绝妙的证明
.
.

小开

在JUnit API中找到:

/**
* ...as the moon sets over the early morning Merlin, Oregon
* mountains, our intrepid adventurers type...
*/
public Test createTest(Class theClass, String name) {
...
}

小开

stop(); // Hammertime!

小开

一个文件中5000多行代码中非常少的一些注释
事实上，我和那个为自己的编码风格辩护的程序员有过一次争论无可奉告! 并且没有评论;-)(或很少)
遗憾的是，这是产品代码

offset=1;
for (i=0;i<=len;i++)
{
if ((i!=0)&&(i<len)) //-3
{
switch(mess[i])
{
case ETX:
case ETB:
case DLE:
buf[offset]=DLE;
offset++;
break;
}
}
buf[offset]=mess[i];
offset++;
}

我喜欢这个开关!

for (n=0;n<offset;n++)
{
Sleep(TR);  //Modif A
Sleep(T);//
FWriteFile(hCom,buf+n,1,&dwMot,NULL);
if (ECHO)
FReadFile(hCom,tab,1,&dwMot,NULL);
}

不，没有注释解释什么“修改A”是在标题。

if (GetFileSize(hSlotFile,NULL)==3600)   //5*720

720是多少?

小开

在为一家芬兰移动网络设备制造商工作期间，我深入研究了硬件抽象层，发现芬兰语单词“puukko”出现了100多次。

“puukko”是一种万能刀，每个芬兰人的工具箱里或家里都有。它被用于从剥土豆到电脑维修(我的观察)的所有事情。我相信在这个语境中，它相当于芬兰语中的“Hack”。

我的芬兰同事否认了这一点，并说这更像是“外科手术/干预”……我差点就相信了，直到我看到下面的评论:

/* Perkele ISO Puukko! */ -> Fucking Big Hack!

小开

在LucasArts的电脑游戏《the Eidolon》(游戏邦注:这款游戏本身就很古怪)的源代码中可以看到……

// He's dead, Jim!

小开

/* My lawyer told me not to reveal */

小开

// I dedicate all this code, all my work, to my wife, Darlene, who will
// have to support me and our three children and the dog once it gets
// released into the public.

小开

//Abandon all hope ye who enter beyond this point

小开

// TODO - Comment this function

小开

为什么你不应该将你的软件开发外包的一个经典案例:

public class Contact
{
//...


/// <summary>
/// Gets or sets the name of the first.
/// </summary>
/// <value>The name of the first.</value>
public string FirstName
{
get { return _firstName; }
set { _firstName = value; }
}
}

小开

Repeat
...
Until (JesusChristsReturn) ' Not sure

小开

-- Change Log:  Not needed. The code is perfect 'cause I wrote it.
-- If you change it, it will break.

我正在检查一些代码注释，以检查它们是否有意义，并看到上面的一行。

小开

long john; // silver

小开

//There can Only Be one HIGHLAN....err..Singleton
public class SomeSingleton
{
...
}

小开

virgin = 0;     /* you're not a virgin anymore, sweety */

小开

i++; // increment variable i

小开

用于政府目的的企业等级系统中的评论

'RH 5/24/06 burn me if this dosn't work.. :)

好RH.....公司总裁/首席开发人员

小开

//open lid




//take sh!t




//close lid

文件打开，数据转储，文件关闭…

小开

在几年前编写Perl时，我在顶部和底部添加了这些注释:

# <magic type="voodoo">


...


# </magic>

下一个研究它的人在Perl中并不是那么热门，他花了一段时间搜索文档，看看“魔法”和“巫毒”是怎么做的。从那以后，我试着添加更多有用的评论……

小开

// Catching exceptions is for communists

从Mike Duncan在SQLite上的页面。

小开

在XSLT文件的头文件中:

DON'T TOUCH THIS SCRIPT -> XSLT is like arcane, black magic

小开

// Hard to explain

它最后也坏了。难怪很难解释清楚

小开

我相信在JBoss的某个地方有一行写着

return null; //Not really null

我一直很喜欢这句话。

小开

 * ...and don't just declare it volatile and think you've solved
* the problem. You young punks think you know what volatile
* means... why in my day we had to cast it volatile uphill
* both ways, and the code still didn't work! Whippersnappers...

小开

// The following strings are meant to be funny.  Do not edit these strings
// unless you are funny, too.  If you don't know if you're funny, you're
// not funny.  If fewer than 2 people unrelated to you have told you that
// you're funny, you're not funny.

小开

在被迫为贫血域对象编写单元测试时，这些对象不过是getter和setter的包(我也是被迫写的):

// zzzzZZZZzzzz....

小开

// human madable inconvenient. Way too sucks.

我仍然没有完全理解它的含义，但我发现它对于许多代码来说是非常正确的。

小开

// I know the line below is wrong, but it came that way from our IP vendor, and
// the driver won't work if you "fix" it. I've had to revert this change 4 times
// now. Leave it alone, or I will hunt you down and hurt you
if (r = 0) {
/* bunch of code here */
}
else
{
/* even more code here */
}

小开

在高斯林的Emacs源代码(警告他编写的超热屏幕管理包不容易理解)中的ascii-art头骨和交叉骨骼(在这里很难重现)。

小开

唐纳德·克努斯的另一个经典作品:

小心以上代码中的bug;

.我只是证明了它是正确的，并没有尝试过

小开

/*
* You may think you know what the following code does.
* But you dont. Trust me.
* Fiddle with it, and youll spend many a sleepless
* night cursing the moment you thought youd be clever
* enough to "optimize" the code below.
* Now close this file and go play with something else.
*/

小开

// set break point here - you'll never reach it

小开

一个奇怪而恰当的有趣错别字:

assert(0); // should never shit this point

小开

// I am not sure if we need this, but too scared to delete.

小开

if(m_measures =/*=*/ --index)
{
....

小开

我记不清了，大概是这样的:

Person p = new Person("John", "Doe", "male");
Collection women = new ArrayList();
women.insert(p.getTail());

这是肮脏的代码;)

小开

/*************************** Drag And Drop Section - Start (you should be me to mess with this section)*********************************************/

小开

if(count<0) count=0;    //don't get me wrong but this has to be done :p

小开

不是注释，而是属性

[ThereBeDragons]

还有一个是我在IHttpHandler的实现中看到的

//What is this?
public bool IsReusable
{
get{return false;}
}

小开

try {
dataSource.close();
}
catch (SQLException ex) {
// Do nothing, since we're going to trash this anyway
}

当然，这类事情实际上是JDBC(或者至少是Oracle的JDBC驱动程序)中的wtf，因为它可以在关闭连接时抛出SQLExceptions…

小开

注意上面代码中的bug;我只是证明了它是正确的，并没有尝试过。

这是唐纳德·克努斯写的。

小开

// Whoever put this here is an idiot...this doesn't work at all !

但是代码还在那里……

小开

用VB写的很好。我今天早上跑进了NET，得到了一个笑声…

''' <summary>
''' Represents an exception that was logged.  Since System.Exception implements IDictionary, it can't be
''' serialized, so I had to write this.  Pretty fucking stupid thing to have to do, System.Exception should
''' be serializable right out of the box, IMHO.
''' </summary>
''' <remarks></remarks>
Public Class LogException

小开

catch (Ex as Exception)
{
// oh crap, we should do something.
}

没有什么比一个空的catch块更能让人觉得代码是健壮的....

小开

/// <summary>
/// The possible outcomes of an update operation (save or delete)
/// </summary>
public enum UpdateResult
{


/// <summary>
/// Updated successfully
/// </summary>
Success = 0,


/// <summary>
/// Updated successfully
/// </summary>
Failed = 1
}

小开

我刚刚注意到自己在写这个

// not brilliant solution, but fair enough heh.

小开

try {


} finally { // should never happen


}

小开

我告诉学员至少做一些异常处理。这是我在每一个db调用....返回

Catch (Exception e) {
//eat it
}

小开

/* Emits a 7-Hz tone for 10 seconds.
True story: 7 Hz is the resonant frequency of a
chicken's skull cavity. This was determined
empirically in Australia, where a new factory
generating 7-Hz tones was located too close to a
chicken ranch: When the factory started up, all the
chickens died.
Your PC may not be able to emit a 7-Hz tone. */


main()
{
sound(7);
delay(10000);
nosound();
}

(Turbo C 2.0版本参考指南中的声音功能)

小开

[onload_1;block=begin;when 1=0]


Some of the techinques in this template are rather obscure, just trust me, they need to be there.
OTOH a better sollution would be to create a few seperate templates and pick one in the php-script...


[onload_1;block=end]

小开

// I don't know why I need this, but it stops the people being upside-down


x = -x;

小开

// This procedure is really good for your dorsolateral prefrontal cortex.

For those of you who are, for some peculiar reason, unaware of the DPC, it's the part of your brain that lights-up when you're deeply engaged in learning something new.

小开

// Any maintenance developer who can't quote entire Monty Python
// movies from memory has no business being a developer.
const string LancelotsFavoriteColor = "$0204FB"

小开

Case 1:
...
break;
...
//I don't want do do this but [my coworker] says it's part of the code standard
default:
break;

小开

来自Java 1.2的SwingUtilities:

doRun.run();  // ... "a doo run run".

小开

不是真的评论:

DvLog::Log("This silly log message fixes a PSCRIPT5.DLL gpf when printing to Adobe.");

可悲的是，没有评论，PSCRIPT5.DLL真的炸了…

小开

'Do not optimize these next two lines. Compiler bugs lurk.

他们做到了。将变量压缩到第二行表达式中会导致跳到堆中间并尝试执行数据。

小开

一些源代码中的德语注释，由机器或非常疲惫的人翻译+谷歌

; Rechnen ja ; have faith in yes

我猜原来的意思是“假设这里是真的”…但从那以后，我就把它当成了人生的咒语。

小开

这是我最喜欢的评论。

/// I intend to do this as shittily as possible because there are many better products that will totally blow this out of the water
/// and we don't have them so whatever

在后面的文件中，我们有更多的乐趣

/// sidestep a bug in WCF (that we can't send types across)
/// or, depending on how you look at, this issue is a Feature

稍后再讲

if( where == null)//be nice

小开

这是我曾经必须支持的实际代码。在努力理解AstaSaysGooGoo和AstaSaysGaaGaa(在那里有更多的astaTempVars被声明和使用)的逻辑之后，我准备放弃。我终于抬头看到了“@author”的评论，整件事开始有意义了。

/*


* @author Andrew Asta
*/
public class AstaClass{


private String astaVar1;
private String astaVar2;
private String astaVar3;
private String astaVar4;
private String astaVar5;
private String astaVar6;
private String astaVar7;
private String astaVar8;
private String astaVar9;
private String astaVar10;


public void AstaSaysGetData(){
//JDBC statement to populate astavars 1 through 10
//...
String astaSqlStatment = "Select astaCol1, astaCol2, astaCol3... From AstaTable Where...";
//..
//...
}


//Perform data manipulation on astavars...
public void AstaSaysGaaGaa(){
[removed for sake of brevity]
}




//Perform more data manipulation on astavars...
public void AstaSaysGooGoO(){
[removed for sake of brevity]
}


public void AstaSaysPersist(){
//JDBC statement to save astavars to DB
String astaSqlStatment = "Update AstaTable set astaCol1 = @astaVar1
, set astaCol2 = @astaVar2
, set astaCol3 = astaCol3...
Where...";
}
}

另外，我更改了实际作者的真实姓名，以避免我陷入任何纠纷等等…

小开

在OLTP数据库事务的主要触发代码中找到:

-- This line negates the @inverseqty, which is the
-- negative of the @insertedquantity.  This works through the
-- magic of the trigger.  In fact, this code is a lot like
-- the bermuda triangle!
@negquantity = -1 * @inverseqty

小开

  mov si, pCard      ; captain?

小开

有一些旧的javascript代码，写得很好。然后是一条评论线

// and there is where the dragon lives

接下来是一个功能，4个人花了一天时间来理解它在做什么。最后我们意识到它根本没用，什么都没有。

小开

在一个著名的商业DOS电子表格应用程序中:

/* This comment was just added in order to check-in a file that was last
checked in by [Insert Programmer FirstName] "Back-to-the-Future" [Insert
Programmer LastName]. While testing for year 2000 problems, he accidentally
checked-in this file while his machine clock was set forward to the year 2000.
This meant that the source code was always newer than the object file and
compiled every time the code was built. I'm checking this file in again to
fix that. */

小开

我继承了一个没有任何UAT交付给客户的项目。它被踢出了栅栏，要求赔偿。

他们第一次使用它，它自然就爆炸了。它是一个插入库，可以覆盖任何以文件名而不是文件描述符作为参数的系统调用。

许多系统调用已经被遗忘。

当我开始使用这款游戏时，它的代码包含了以下内容:

/* core dumps around here but this is hardly ever called */

而且