This ends the section on error handling.
至此，错误处理一节全部结束。
Failing to design proper error handling.
没有设计正确的错误处理。
More error handling and clean-up code is required.
需要更多错误处理和清理代码。
Detailed error handling built into the application.
应用程序中内建了详细的错误处理机制。
Inefficient error handling makes debugging difficult.
无效的错误处理让调试十分困难。
setErrorHandler(): This is the key for error handling.
setErrorHandler()：这是错误处理的关键方法。
Leverage both client - and server-side error handling.
同时利用客户端和服务器端错误处理。
This is an implementation of rudimentary error handling.
这是基本错误处理的实现。
Set aside runnables and memory areas for error handling.
为错误处理预留runnable对象和存储区。
Enhanced error handling through the use of SQL handlers.
通过使用SQL处理程序增强了错误处理能力。
Do not over-engineer a common utility for error handling.
不要针对错误处理过度构建某个常用实用工具。
This brings me to the second anti-pattern in error handling.
这就带来了错误处理中的第二种反模式。
To build strong error handling, you need a layered approach.
为了建立强大的错误处理机制，需要采用分层的方法。
This article looks at validation, error handling, and schemas.
本文考察验证、错误处理和模式。
First and foremost, there is no error handling for JSONP calls.
第一，也是最重要的一点，没有关于 JSONP 调用的错误处理。
You might also want to improve the error handling in the plug-in.
可能还需要在插件中改进错误处理功能。
Strong error handling translates into more reliable applications.
强大的错误处理可以形成更可靠的应用程序。
For the example, the command is as follows (with error handling).
对于本实例而言，命令如下(具备错误处理)。
So you might use this in your error handling like Listing 9 details.
在错误处理中可以使用这些信息，如清单9所示。
Exceptions provide a whole new way of thinking about error handling.
异常为考虑错误处理提供了一种全新的方法。
This support provides for improved error handling in a more consistent way.
这项支持允许以更一致的方式实现更好的错误处理。
The second part to component level error handling is to do appropriate logging.
组件层出错处理的第二个部分就是要做适当的日志。
LEI administrators will also welcome improved failover and better error handling.
LEI管理员还将欢迎改进的故障转移和更好的错误处理。
PDO offers 3 different error handling modes to suit different styles of programming
PDO提供了3种不同的错误处理模式，以满足不同风格的编程
Listing 10 demonstrates the complete finished program, including all error handling.
清单10展示了完整的程序，包括所有错误处理。
We have not mentioned error handling, but this is clearly necessary in several places.
我们还没有介绍错误处理，但是在某些情况下这个功能非常必要。
However, asynchronous interaction pushes more complex error handling onto the consumer.
然而，异步交互将更复杂的错误处理推给了用户。
More importantly, the error handling approaches are ill-defined and again vary drastically.
更重要的是，错误处理方法是模糊不清又变化巨大的。
Faults and error handling are covered in more detail in a subsequent article in this series.
将在本系列的后续文章中更详细地对错误和错误处理进行讨论。
The following sections further describe each error handling construct in solidDB procedures.
后面的小节将进一步描述solidDB 过程中的每一种错误处理。
应用推荐