/**
 * Happy Javadoc haiku:
 *
 * Without Javadoc
 * Builds break in Maven site stage
 * This fixes the build.
 */

我经常看到这种情况:

// TODO make this work

写得很好的Lisp是最容易阅读的语言之一，我喜欢它。但是写得不好的Lisp可能是比糟糕的Java更糟糕的噩梦，等等。

在这里，我们需要创建一个“组文件”，如果一个原始文件有3个变体，后缀为a, b和c。我一直试图追踪一个奇怪的错误，我们得到了不必要的组文件……

  (let ((varianta (format nil "~aa" problem))
        (variantb (format nil "~ab" problem))
        (variantc (format nil "~ac" problem)))
    ;;if the A and B variants exist, create a group file
    ;;(why not just check for a? I don't know, this just feels right)
    (when (and (probe-file varianta)
               (probe-file variantb))
      ...)))

Bug: 1, Gut: 0。

显然，写这篇文章的人没有想到，也许检查所有三种变体是一个好主意。当然，这是我在最初编写这段代码十年之后(它比第一个SVN日志更早)最终追踪到的错误。

[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]

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

// He's dead, Jim!

我前几天刚检查过这个…

/// <STERNLY-WORDED-WARNING>
/// Pay attention to this or I will hunt you down.
/// ...
/// </STERNLY-WORDED-WARNING>

(“……”== "专有的东西，我不能发布")。我只是喜欢我的措辞严厉的警告元素。