It was a diabolical error, a schoolboy error.
那是个糟糕透顶的错误，一个小学生才会犯的错误。
Instead of human being's counting error, which only results one or two counting error in number, an error in the program code could cause tramendous error in number.
人类的计数错误只会导致一到两个数字错误，而程序代码中的一个错误可能会导致数字上的严重错误。
Unfortunately, you do not receive an explicit error message if this error condition occurs.
不幸的是，出现这种错误条件时您不会收到明确的错误消息。
This is not to say to never include information such as error codes in the error message.
这并不是说，永远不要在错误消息中包含像错误代码这样的信息。
Previously, the application would not have detected this error until execution, producing error messages and a storage dump.
以前，应用程序只有到执行时才会检测到此错误，并产生错误消息和一个存储转储。
Error code 18456 within this error means it has to do with a failed login.
这个错误中的错误码18456表示它必须处理一个失败的登录。
But, you can't overlook a key element in an error response strategy — when an error occurs.
但您不能忽视错误响应策略中的一个关键元素——错误发生的时间。
For this reason, we recommend that KIOSK applications have their own error messages or error pages.
基于这个原因，建议KIOSK应用程序要自定义错误信息或者错误页面。
But others use standard out and standard error to show progress and error messages, in that order.
但其他的一些命令则使用标准输出和标准错误，并按顺序显示处理过程和错误消息。
If a set timeout or error occurs, an error message and refresh button are displayed to the user.
如果超过设置的时间或出现错误，将显示一条错误消息，并向用户显示刷新按钮。
Perhaps it's a logic error or an error caused by interacting with the operating system or both.
可能它是一个逻辑错误和/或与操作系统进行交互所导致的错误，或两者兼具。
But you see, it was just an error, a stupid error, the kind anyone could make.
所以你瞧，这仅仅是个错误，一个愚蠢的错误，那种人人都可能犯的错误。
Error handling by the mediation components mostly involves transforming the provider error structures into well defined error structures defined in the context of business domain.
由协调组件完成的错误处理一般都包含将提供者错误结构转换成在业务域的上下文中明确定义的错误结构。
This article shows you how to identify the component where the hang occurs and determine whether it is due to user error, programming error, or a bug in the product.
本文向您展示如何识别发生挂起的组件，并判定挂起是因为用户错误、设计错误，还是因为产品中的缺陷。
The exact error code, the error text, and even the line that caused the error can be retrieved.
可以检索精确的错误代码、错误文本甚至导致错误的那一行。
Error hiding - Disguising error messages sent by the server.
错误隐藏——伪装成服务器发出的错误消息。
If you happened to make an XML coding error, you will see an error output instead.
如果您发现了一个XML编码错误，您将看到一个输出错误。
Poorly worded error messaging and inconsistent error signposts can make it hard for users to understand when an error has occurred.
含义不明的错误消息和不一致的错误标志都会让用户弄不清楚何时发生了错误。
So fatal errors fall under that second principle of good error handling: error handling isn't disruptive... unless it has to be.
所以，致命错误归于第二个优秀错误处理原则：错误处理是不中断的，除非有必要。
Diagnostics improvements - More information is provided in error messages when a composition error occurs.
诊断功能上的增强——当组合错误发生时将提供更多的错误信息。
Given that, you're left with the third principle of error handling: error handling is informative.
下面是错误处理的第三个原则：错误处理要有告知性。
That won't cause a fatal PHP error, but it is a coding error!
虽然这不会造成严重错误，但这是一个编码错误。
Table 1 Outlines the ways to retrieve an error from the error stack.
表1略述了从错误栈检索错误的方法。
Error Logger - Tracks redirection to error pages.
错误日志程序 –跟踪错误页面的重定向。
A warning in SAX is defined as any problem that is not considered an error or fatal error as defined by the XML 1.0 recommendation.
根据XML 1.0推荐标准定义，SAX中的警告被定义为不属于错误或致命错误的问题。
Error (control, args) - Displays an error on the console.
error (control,args)—在控制台显示一条错误。
Error . Returns the associated error message.
Error，返回相关的错误消息。
Rather than simply proclaiming "ERROR 6534," the error message can explain, "Please reference error number 6534 if you address this problem with the help desk at extension 555."
不要简单地显示 “ERROR 6534”，而是可以在错误消息中解释 “拨打分机 555 向帮助台咨询此问题时，请引用错误号 6534”。
The following example shows the CLPPlus behavior during an OS error with exit error code.
以下示例使用exit错误代码显示了出现OS错误期间的CLPPlus行为。
In addition to setting the error code, PDO will throw a PDOException and set its properties to reflect the error code and error information.
除了设置错误代码以外，PDO还将抛出一个PDOException，并设置其属性，以反映错误代码和错误信息。
应用推荐