在一个著名的商业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. */

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

后面是四个嵌套的for循环

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

// zzzzZZZZzzzz....

try {

} finally { // should never happen 

}

using namespace std;            // So sue me

/// <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
}