签名的第一部分(位于尖括号 ‘<...>’ 内)就是该类的类型参数定义清单。
The first part of the signature (within the angle brackets '<...>') is just the list of type parameter definitions for the class.
现在考虑一下,如果使用注释来定义清单4和清单5的绑定,将涉及哪些内容。
Now consider what would be involved in using annotations to define the Listings 4 and 5 bindings.
Dropdown的值要么被服务调用动态寻回,要么处于用控制器的静态定义清单中。
The values of the dropdown can either be dynamically retrieved by service invocation, or they can be in a statically defined list with the control.
接下来,我将定义清单6所示的测试用例,它也包含一个参数,用于进行测试的应用程序的基url。
Next, I define the test case shown in Listing 6, which also takes a parameter for the base URL of the application under test.
因此,如果在系统中定义清单9中的事件,那么在发生system -scaleup事件时,会执行指定的处理函数。
So if the event in Listing 9 is defined in a system whenever an event with the name system-scaleup happens, the specified handler is executed.
还有一种更加复杂的结构定义,如清单13中所示。
And a much more complex structure definition, as shown here in Listing 13.
该函数的定义如清单10所示。
管理员还可以定义每个清单在网站上显示的时间长度。
Administrators can also define the length of time that each listing is visible on the site.
牢记正确的缩进,定义应当类似清单5。
Keeping in mind the proper indentation, the definition should look like Listing 5.
处理弹出窗口的过程定义在清单12中。
The procedure to handle a pop-up window is defined in Listing 12.
该扩展的完整定义如清单4所示。
The full definition of the extension can be seen in listing 4.
在深入讨论语义之前,先来看一下修改后的队列定义,见清单6。
Before delving more deeply into the semantics, let's look into the modified queue definition, shown in Listing 6.
由于当前内存模型的定义,清单7中的代码无效。
The code in Listing 7 doesn't work because of the current definition of the memory model.
清单8定义这个对象的API。
在HTML模板内对该菜单的定义如清单29所示。
The definition of the menu in the HTML template can be as in Listing 29.
所生成的WSDL定义中的XML数据类型定义如 清单8 所示。
The XML datatype definition in the generated WSDL definition looks like Listing 8.
使用这些定义,清单1可以重写成这样。
下面的类定义(清单1)演示了这个用于定义跟踪日志记录器和消息日志记录器的方法。
The following class definition (Listing 1) demonstrates this method for defining trace and message loggers.
清单16定义日志位置。
stop - server任务的详细内容定义在清单10中。
示例bean定义与清单7中的代码类似。
The sample bean definition looks like the code in Listing 7.
start - server任务的详细内容定义在清单8中。
The details for the start-server task are defined in Listing 8.
由于peek还没有定义,因此清单21还不能编译。
Because peek hasn't been defined yet, the code in Listing 21 won't compile.
sigaction结构体的定义如清单3所示。
这个策略集在 definitions.xml 中定义,如清单 7 所示。
现在,看一下push方法的定义,见清单8。
Now, look into the definition of the push method, shown in Listing 8.
清单4.定义swap !
对它进行定义,如清单2所示。
这个示例场景中的处理程序定义文件如 清单3 所示。
The handler definition file in the example scenario is shown in Listing 3.
对它进行验证和定义,如 清单13 所示。
应用推荐