| 1. | The class annotation is at position 0 , and the method annotation is at position 1
类注释在位置0 ，方法注释在位置1 。 |
| 2. | Whose purpose was to describe the use of the type . a much better type would be
的注释类型，这类注释的用途是描述类型的使用。 |
| 3. | Even before you get around to processing such annotations at the semantic level , you can use them in documentation tasks
即使在准备从语义层面上处理这类注释之前，也可以在文档任务中加以利用。 |
| 4. | If the previous two types of comments are not found in the code , intellisense will display end - of - line comments in the definition
如果未在代码中找到前两类注释，则intellisense将显示定义中的行尾注释。 |
| 5. | This makes it hard to develop software that can use these annotations to drive decisions about the semantics of the schema
仅仅提供了非正式的描述，需要人们读懂后才能使用。因此很难开发能够使用这类注释推断模式语义的软件。 |
| 6. | Finally , if none of the previous types of comments appear in the code , intellisense will display comments that appear directly above the definition with no blank lines in between
最后，如果前面几类注释均未在代码中出现，则intellisense将显示出现在定义紧上方（无空行）的注释。 |
| 7. | In practice , however , wordnet is not necessarily the best choice for such annotations ; most often the terms used in schemata have specific technical meanings that are not covered in such a general purpose dictionary
不过，在实践中， wordnet并不一定是这类注释的最佳选择，模式中使用的术语多数都有专门的技术含义，而通用词典中并没有记载这些含义。 |
| 8. | To really make it useful , i d want to minimize the number of annotations required , perhaps by using a class annotation to flag the classes where i want the method generated in combination with individual field annotations to override the default handling of fields
为使它真正有用，我情愿最小化所需的注释数目，可能通过使用类注释来标志我想要在其中生成方法的类，并使用单个的字段注释来重写字段的默认处理。 |
