总的来说，我更愿意自己编写注释。
编写注释：回忆以前编写的脚本时。
Writing comments: when your script flashes before your eyes.
接下来，将需要为所确定的每个注释编写注释处理程序。
Next, you'll need to write annotation handlers for each of the annotations you've identified.
收集的标题注释行数将因编写注释所使用的语言而异。
The number of header comment lines collected will vary depending on the language in which the comments are written.
然后您可以用一种将注释成功地写到生成的样式表中的格式重新编写注释生成器。
You can then rewrite your comment generator in a form that is successfully written out to the generated stylesheet.
开发人员通过Eclipse工作台在本地使用代码，包括的工作有创建新资源、修改现有资源、编写注释，并在他们使用后在本地保存这些内容。
Developers work with code locally via the Eclipse workbench, creating new resources, modifying existing ones, writing commentaries, and saving locally as they go.
那么，如果您正在编写代码，而又没有上司或公司的规定可以做指导，这时，又该如何注释呢？
So, if you are writing code, in the absence of a boss or a company policy telling you what to do, how do you comment it?
显然，您可以编写样式表来扫描整个跟踪输出，查找注释以及对它们进行排序和计数。
Obviously, you could write a stylesheet that scanned through the traced output, found the comments, and sorted and counted them.
尽管他在文化编程方面的工作没有赶上他最初的贡献，但这无疑影响到了我们对编写和注释程序的考虑。
Although his work on literate programming has not caught on in his original form, it has definitely influenced the way many of us think about writing and annotating programs.
就覆盖缺省行为而言，开发人员的工作效率得到进一步提高，因为可以使用注释而不是编写代码来方便快捷地完成缺省行为覆盖。
Developer productivity is further enhanced when it's time to override the defaults, since this can be accomplished quickly and simply using annotations rather than writing code.
毫无疑问，你已经千百次地被告知，在编写代码时一定要添加注释。
I'm sure you have been told a number of times that you should write comments in your code.
唯一需要使用内联注释是在你编写了非常复杂的算法，你需要在代码旁边记录说明你的想法。
The only legitimate use of inline comments is when you have some very complex algorithm that you need to have some thoughts about beside the code.
除了注意到我的选项卡设置可能与编写此文件的其他人员的设置不匹配之外，您将看到若干标准错误值、其符号名称，以及分别描述各个值的简短注释。
In addition to noticing that my TAB Settings don't match those of whoever wrote this file, you'll see several of the standard error values, their symbolic names, and a brief comment describing each.
举例来说，以统一的格式编写的代码较之仓促编写的代码(缺少注释、适当的缩进等)更有价值。
As an example, writing code that is formatted in a consistent manner is more valuable than code that was written in a hurry — lacking comments, proper indentation and the like.
编写定制的注释器是解决特定业务问题的有效方法。
Writing custom annotators can be a useful way to solve a specific business problem.
要加上足够的注释，这样以后就可以轻松地想起原来编写代码的原因。
Comment your code heavily so that at a later date, you can easily remember the reason your source code was written as it is.
但是在编写自己的注释类型时，注释类型的目的并不总是显而易见的。
However, as you move into writing your own annotation types, the purpose of your annotation types isn't always self-evident.
在本系列文章的第2部分，我将详细说明Tiger对编写自己的注释类型的支持。
In Part 2 of this series. I'll detail Tiger's support for writing your own annotation types.
依照上述关于注释的说明，您可以编写一个简单的Jython服务(如下所示)，并借助Jython部署程序将它公开为Web服务。
Based on the above instructions on annotations, you can write a simple Jython service, given below, and expose it as a Web service with the help of the Jython deployer.
writeProcessingInstruction和writeComment方法可以分别编写实体引用、过程说明和注释。
Methods writeEntityRef, writeProcessingInstruction, and writeComment can write entity references, processing instructions, and comments, respectively.
通常，使用JSP文件和条件语句而不是通过编写需要被应用的注释来编写portlet源代码看起来要更容易更快。
Often, it would seem easier and faster to write the portlet source using a JSP file and conditional statements, instead of writing an annotation that needs to be applied.
如果您编写了大量BindingAnnotations，就会得到许多这样的小文件，每个文件只是注释名称不同。
If you write a lot of BindingAnnotations, you'll wind up with a lot of these little files, each of which differs only in the name of the annotation.
使用Groovy编写测试会带来实际的效益，不管是GroovyTestCase或包含注释的JUnit 4 .x测试用例。
There are real benefits to writing your tests in Groovy, whether it is a GroovyTestCase or a JUnit 4.x test case with annotations.
ZWS演示了一个即使是使用500多行带足够注释的zsh(！)编写的应用程序——在这里是一个HTTP 0.9 +服务器——也可以有多强大。
ZWS demonstrates how capable an application — in this case, an HTTP 0.9 + server — can be even though written in just over 500 lines of well-commented ZSH (!).
以前，为了使用静态SQL，需要用pureQuery 带注释的方法样式来编写应用程序。
Previously, you needed to write your application in the pureQuery annotated-method style to use static SQL.
要部署和发布一个JAX-WSWeb服务，您只需要编写经过注释的 Web 服务实现即可。
The annotated Web service implementation is all you need to write to deploy and publish a JAX-WS Web service.
Tiger包含内置注释，还支持您自己编写的定制注释。
Tiger includes built-in annotations and also supports custom annotations you can write yourself.
示例中大量的注释对编写文章或教程的各个方面提供了指导。
Extensive comments in the samples guide you through every aspect of coding your article or tutorial. Here are some other tips you might find helpful.
无论能否带来语义透明性，为模式编写良好的注释都非常重要。
Good annotations of schemata are very important, regardless of whether or not they lead to semantic transparency.
不过JSON允许一些额外的结构(特别是注释)，它们可能会被一些不那么小心的JSON编写者误输入了。
But JSON allows for a few extra constructs (particularly comments) that mean this will miss input from some less-than-careful JSON creators.
应用推荐