Then it gives control to the exception handler 然后它把控制权交给异常处理器。
The exception handler gains control 异常处理器得到控制权。
Control then flows to the next statement after the exception handler and continues within your program 控制然后继续按照你的程序中的(位于)异常处理器的下一个声明。
Whenever an exception occurs , the kernel searches the list of exception frames for an exception handler 无论什么时候异常发生,这个内核位一个异常处理器搜索这个异常结构的列表。
Once the kernel locates an exception handler , it unwinds the execution and exception frame stacks in parallel , calling cleanup handlers along the way 一旦内核定位了一个异常处理器,它平行展开这个异常和异常结构,按照情形调用清理处理器。
Neither your exception handler code nor the code following it would have been executed : either the system would have crashed or some higher - level handler would have taken over 无论你的异常处理器代码还是它之后的代码被执行:活着操作系统崩溃活着一些高级别的处理器将接管。
In the preceding example , had you returned the value exception _ continue _ search , the operating system would have continued unwinding the stack looking for an exception handler 在之前的例子中,你已经返回了值exception _ continue _ search ,操作系统将继续解除这个查找异常处理器的堆栈。
Closely integrated with the compiler ' s code generator , structured exception handling lets you easily place a guard on sections of your code and invoke exception handlers when something goes wrong in the guarded section 用编译器的编码发生器紧密结合,结构异常处理使你轻易的在你的代码区域上放置一个防护装置,并且当被防护的区域内出现错误的时候调用异常处理器。