例如，要在代码中包含尖括号。
节点类型用双层尖括号括起。
我从未想过有人愿意在尖括号中写代码。
I never imagined that anybody would want to write in anchor brackets.
你也许认为HTML就是标签或尖括号。
但它不使用方括号和圆括号，而是使用尖括号。
But instead of brackets or parentheses, you use curly braces.
尖括号不能是宏展开。
这种代码使用许多尖括号、引号和前斜线来编写。
This is a code that makes much use of Angle brackets, quotation marks and forward slashes.
尖括号内应为类型。
例如，HTML使用尖括号把html标签括起来。
在元素标记中左尖括号字符“<”之后不能有空白。
White space cannot follow the open angle bracket character '<' in an element tag.
在前面的结果中，对这些记号的引用是用尖括号括起来的。
References to these tokens in the preceding productions are enclosed in angle brackets.
尖括号为由 “T”参数类型表示的泛型指定具体类型。
The angle brackets assign a specific type (that is, the parameterized type) to the generic type represented by the "T" argument types.
要标记元素的开始标记，像这样将元素名放到尖括号中（）：。
To mark the beginning tag of the element, place the element's name inside angle brackets () like this: .
属性来指定诸如左尖括号和右尖括号等分隔符，以封装对象名称。
Properties to specify delimiters such as a left bracket and a right bracket to encapsulate the object name.
您可以看到双尖括号和空格是如何根据URI的标准格式进行转义的。
You can see how the Angle brackets and whitespace are escaped according to URI standard form.
从图形上看，构造型用包围在尖括号中的关键字表示，比如图1中的。
Graphically, stereotypes are indicated by a keyword in Angle brackets, such as in Figure 1.
实际上，策略表达式只是使用一个尖括号格式的逻辑表达式，断言是子句。
Policy expressions really are just logic expressions using a pointy-bracket format, with assertions as clauses.
客户端代码必须通过指定尖括号中的类型参数来声明和实例化构造类型。
Client code must declare and instantiate a constructed type by specifying a type argument inside the Angle brackets.
每一通则均有相应的鉴别号，在章节名称的后面的尖括号中，如色谱法。
Each general chapter is assigned a number that appears in Angle brackets adjacent to the chapter name (e. g., Chromatography).
实际上，策略表达式只是使用一个尖括号格式的逻辑表达式，断言是子句。
Policy expressions really are just logic expressions using a pointy - bracket format, with assertions as clauses.
一些差异相对来说很小，比如圆括号代替了尖括号；而另一些则是针锋相对的。
Some of the differences are relatively trivial — parentheses instead of Angle brackets, for example — while others are ambivalent.
换句话说，firstName元素总是缺少结束标识，或缺少开头的尖括号。
In other words, an opening firstName element is never closed or an opening Angle bracket is missing.
签名的第一部分（位于尖括号 ‘<...>’ 内）就是该类的类型参数定义清单。
The first part of the signature (within the angle brackets '<...>') is just the list of type parameter definitions for the class.
当左尖括号字符“<”与元素标记的第一个字符之间出现空白时，便会发生此错误。
This error occurs when white space appears between the open angle bracket character '<' and the first character of the element tag.
注意：尖括号中的参数为可选参数；方括号()中的参数或选项为必需参数，必须提供。
Note: parameters shown in Angle brackets are optional; parameters or options shown in normal brackets () are required and must be provided.
事件序列是放在尖括号中的字符串，例如，或者
The event sequence is a string enclosed in angle brackets, such as or <Shift-Button-3>.
下一个括弧括起来的子表达式和上一个实例非常相似：要么匹配不包括尖括号的所有字符 ?
The next parenthesized sub-expression is very similar to the one above.
就像泛型类的类型参数用尖括号括起来那样，泛型类型应用程序的参数也是用尖括号括起来的。
Just as the type parameters of a generic class are wrapped in Angle brackets, the arguments of a generic type application are wrapped in Angle brackets as well.
至少要花和实际数据同样多的时间来处理尖括号和标签名称，有可能使本来很少的输入变得非常大。
You're spending at least as much time dealing with Angle brackets and tag names as you are with actual data, and the potential to make little typos is tremendous.
如果它们有uri，那么它们必须表示为您在清单1中看到的形式：用尖括号将绝对URI引用括起来。
If they have a URI, they must be presented in the form you see in Listing 1: the absolute URI reference enclosed in Angle brackets.
应用推荐