不用在相同的方法中使用编程事务，而是将更新操作移动到调用栈的另一个公共方法中。
Rather than using programmatic transactions within the same method, you can move the update operations to another public method within the call stack.
通过此技巧，您可以有效地在调用栈的较低层次开始事务，从而减少花费在数据库中的时间。
With this technique, you are effectively starting the transaction at a lower level in the call stack, thereby reducing the amount of time you are in the database.
始终在调用栈的最高层(api层)启动事务有时会效率低下，特别是对于具有高用户吞吐量和高数据库并发性需求的应用程序。
Always starting transactions at the highest level in the call stack (the API layer) can be inefficient, particularly in cases of high-user-throughput and high-database-concurrency needs.
调用栈的检查在遇到PrivilegedAction实例时停止，有效地将执行指定操作所必需的许可权授予所有的后继类调用。
The check of the calling stack stops when it encounters a PrivilegedAction instance, effectively granting all subsequent class calls the required permission to perform the specified operation.
通过这种方式，如果一个设计调用一个主机栈，您可以替换一个协调的虚拟机系统。
In this way, if a design calls for a hosting stack, you can substitute a compatible virtual system.
如果不使用引用，就需要将整个数组或hash 表复制到该函数的调用栈中，然后在函数中再次对其进行复制。
Without a reference, you copy the entire array or hash onto the function call stack, and then copy it again in the function.
您是否了解应如何有效利用Rubinius清晰可见的内部结构，例如可以在运行时刻访问并修改字节码、查看调用栈？
Do you have ideas what you could do with Rubinius' transparency and accessible internals, i.e. accessing and modifying bytecode at runtime, inspecting the call stack etc.?
添加stack_depth：3参数，限制调用malloc时收集的栈跟踪。
You add the stack_depth: 3 parameter to limit the stack trace collected when a malloc is called.
Job Watcher与Collection Services收集的数据大致相同，但收集的信息更详细，比如调用栈和sql语句。
Job Watcher collects much of the same data that Collection Services does but also collects more detailed information, such as call stacks and SQL statements.
应用程序中的每个线程都需要内存来保存它的栈(用于在调用函数时保存本地变量和维持状态的内存区)。
Every thread in an application requires memory to hold its stack (the area of memory used to hold local variables and maintain state when calling functions).
每当实际代码碰到任何类型的错误，它就抛出一个异常，然后该异常就进入调用栈。
Whenever the actual code encounters any type of error, it throws an exception, which then goes to the call stack.
这对调试器来说是难以置信地有用-它意味着调用栈完全可靠，即使你没有正被调试的所有模块的符号。
This was unbelievably useful for debuggers - it meant that call stacks were quite reliable, even if you didn't have symbols for all the modules being debugged.
当函数返回到进行调用的函数时，后者一定不能依赖于仍在栈中的参数列表。
The calling function must not depend on the parameter list still being on the stack when your function returns to it.
有一点要注意：数组的第一个元素（而不是最后一个元素）是这个调用跟踪的栈顶。
One thing to note: the first element of the arrray is the top of the call trace, not the last.
但是，即使是不可取消的任务也应该尝试保留中断状态，以防在不可取消的任务结束之后，调用栈上更高层的代码需要对中断进行处理。
However, even noncancelable tasks should attempt to preserve the interrupted status in case code higher up on the call stack wants to act on the interruption after the noncancelable task completes.
当句柄范围的析构函数被调用时，所有在那个范围中创建的句柄都将被从栈中移除。
When the handle scope's destructor is called all handles created within that scope are removed from the stack.
在程序的正常操作过程中，当调用一个函数时，被调用函数的所有参数以及返回位置的指针都放在栈中。
During normal operation of a program, when a function is called, any arguments for the called function along with a pointer to the return location are placed onto the stack.
要使操作成功完成，调用栈中的每个类必须有必需的许可权。
Each class in the calling stack must have the required permissions for the operations to complete successfully.
栈顶的地址就代表最后一次被调用的函数（也就是当前的活动函数）。
The address at the top of the stack represents the function that was last called (that is, the active function).
这意味着我们必须手工重新编写栈来仿造一个返回地址，以使得尾部调用的函数能直接返回到调用它的函数。
This means that we have to manually rewrite the stack to fake a return address so that the tail-called function will return directly to our parent.
在尾部调用之后除去栈结构的方法称为尾部调用优化。
The idea of removing stack frames after tail-calls is called tail-call optimization.
好像一旦控制权传递给了尾部调用的函数，栈中就再也没有有用的内容了。
It seems that once control is passed to the tail-called function, nothing in the stack is useful anymore.
您可以选择调用栈中的条目，这样可以显示变量被调用时的值。
Entries on the call stack can be selected, causing variables at the time of invocation to be displayed.
执行流程经过定义了配置的对象栈，其作用是接收调用并执行一些处理，然后继续传递。
The flow of execution passes through a configuration-defined stack of objects whose purpose and design is to accept an invocation, do something with it, and then pass it on.
通道参数实际上更像是全局区，只不过在模板调用栈中可以改变它的值。
Tunnel parameters are actually more like a global pool, except you can change a value as you go further in your stack of template invocations.
调用栈将异常传递给catch块，异常正是通过这种方式被返回给用户的。
The call stack passes the exception to the catch block, and that is how it gets returned to the user.
最后的调用（尾（tail））只是调用函数，没有任何过程调用或栈维护开销。
The last call (the tail) simply invokes the function without any procedure call or stack maintenance overhead.
Quantify 使我们能够了解到在调用栈中对于每一个部分的执行的最大和最小的时间，被派生的时间消耗和其他有用的信息。
Quantify enabled us to understand the maximum and minimum times for execution at each step in the call stack, the time consumed by descendents, and other useful pieces of information.
Quantify 使我们能够了解到在调用栈中对于每一个部分的执行的最大和最小的时间，被派生的时间消耗和其他有用的信息。
Quantify enabled us to understand the maximum and minimum times for execution at each step in the call stack, the time consumed by descendents, and other useful pieces of information.
应用推荐