| 1. | Display the current call stack of programs and functions
显示程序和函数的当前调用栈。 |
| 2. | You re literally going back to a previous call stack
也就是直接返回到一个先前的调用栈。 |
| 3. | Entries on the call stack can be selected , causing variables at the time of invocation to be displayed
您可以选择调用栈中的条目，这样可以显示变量被调用时的值。 |
| 4. | A continuation lets you capture execution state with instance variables and a call stack at any point in time
延续让您能够在任何时刻及时捕获执行状态（使用实例变量和调用栈） 。 |
| 5. | Unlike the java language , squeak uses a dynamic data structure instead of a call stack , but the concept is the same
（与java语言不同， squeak使用动态的数据结构代替调用栈，但概念是一样的。 ） |
| 6. | Cross - language debugging support in the same call stack , such as mixing of java and sql nested stored procedure calls
相同调用栈中的跨语言调试支持，例如java和sql嵌套存储过程调用的混合使用。 |
| 7. | Without a reference , you copy the entire array or hash onto the function call stack , and then copy it again in the function
如果不使用引用，就需要将整个数组或hash表复制到该函数的调用栈中，然后在函数中再次对其进行复制。 |
| 8. | Notice , for example , that the debug view not to be confused with the debug perspective shows the call stack ; this combines the frames and threads that you are familiar with in idea
例如，注意， debug视图（请不要与debug透视图混淆）显示了调用栈的情况；这些信息实际上包括了您熟悉的idea框架和线程的内容。 |
| 9. | Because most stacks are the same , you don t actually have to store very much data - at most a few thousand strings - identifying call stacks and the associated numbers of instances linked to each stack
因为多数栈都是相同的，标识调用栈以及链接到每个栈的相关实例个数需要存储的数据并不很多（最多几千个字符串） 。 |
| 10. | It s hard enough to rely on your own programming skill or that of your co - workers ; it s scary to have to rely on the documentation skill of anyone whose code you might be using sixteen frames down the call stack as your primary error - handling mechanism
依赖于您自己的或者您的合作伙伴的编程技巧是非常困难的；如果不得不依赖于某个人的文档化技巧，那么对于他的代码您可能得使用调用栈中的十六个帧来作为您的主要的错误处理机制，这将会是令人恐慌的。 |
