1·This mode is often used for global variable access, branching, and subroutine calls.
这种模式通常用于全局变量访问、分支以及子程序调用。
2·Let's take a look at the subroutine and describe how it works.
让我们来看一看这个子程序并了解一下其工作原理。
3·Recall that the fields are delimited by ##, and the subroutine above puts all of the fields for one record into the delRecs array.
字段都是用 ## 分隔的，并且上面的子程序将把一条记录的所有字段放入 delRecs 数组中。
4·The stack region is used for subroutine return addresses, as well as to store automatic data.
stack区域用于子程序返回地址，也用于存储自动数据。
5·Once the keyword and display parameter hash has been built, we can move on to our simple keyword matching subroutine: matchWords.
构建了关键字和显示参数散列之后，接下来我们可以查看简单的关键字匹配子程序：matchWords。
1·Number of times that the process was dispatched (or how many times the kernel dispatch subroutine relinquished the CPU to that process).
进程被调度的次数(或者说是内核调度子例程为那个进程释放CPU的次数)。
2·At this level a program becomes multiple instances of a service subroutine callable in parallel by a client through some grid middleware.
这个级别上的应用程序已经变成服务子例程的多个实例，可由客户机通过某种网格中间件并行调用。
3·Listing 3 shows the variable declaration and subroutine calls from the program header.
清单3显示了程序头文件中的变量声明和子例程调用。
4·The END() subroutine executes when the script terminates and ensures that a DBI error message about not explicitly disconnecting from the database doesn't occur.
当脚本终止并且确保没有出现关于数据库未显式分离的 DBI 错误消息时， END() 子例程就会执行。
5·Listing 4 shows two rules from the same subroutine of standardizing part names.
清单4显示了来自同一个标准化部件名称的子例程的两条规则。