So you might use this in your error handling like Listing 9 details.
在错误处理中可以使用这些信息，如清单9所示。
Without that baseline, the check option reports the error shown in Listing 1.
如果没有基线，检查选项会报告清单1所示的错误。
The reason for this change is that if you try to redirect the browser, you get the the runtime error that Listing 18 shows.
之所以作这样的改变，是因为如果您重定向浏览器，将会遇到列表18所示的运行时错误。
To do this, make a HEAD request and then check for a 404 error in your callback function; Listing 11 shows a sample callback.
要实现这种功能，生成一个HEAD请求，然后在回调函数中检查404错误；清单11给出了一个简单的回调函数。
Listing 10 demonstrates the complete finished program, including all error handling.
清单10展示了完整的程序，包括所有错误处理。
Listing 6 shows the translation for the error message when the user specifies an incorrect news type.
清单6显示了当用户指定了错误的消息类型时错误消息的翻译。
It's important to distinguish between informational, warning, and error messages, as shown in Listing 5, above.
区别信息性消息、警告消息和错误消息十分重要，如上述清单5所示。
If you just used the command as in Listing 16, then you would get an error.
如果您像清单16那样使用该命令，那么将得到一个错误。
Adding an exception to the trace logger (Listing 3) prints the error message along with a full stack trace.
把异常添加到跟踪日志记录器(清单3)打印出错误消息和完整的堆栈跟踪。
This script shown in Listing 4 has no error checking and is not very robust, but it illustrates our point.
该脚本如清单4所示，它没有任何错误检查机制，也不是非常稳定，但是它足以满足我们的演示需要。
This code generates the following JSON data shown in Listing 8, assuming an error condition is present.
这些代码生成如清单8所示的JSON数据，假设给出了一个错误条件。
The XSL stylesheet shown in Listing 8 obtains the specific error message that explains why the validation action failed and returns it to the client that issued the request.
清单8中显示的xsl样式表包含具体的错误消息，可以解释验证动作为何失败，并将它返回给发出请求的客户机。
An example error is depicted in Listing 3.
清单3描述了一个错误实例。
The programmer received the error compile listing report.
程序员接收到错误的编译清单报告。
Listing 2 adds a class to the source shown in Listing 1 and registers that error handler with the parser.
清单2在清单1中所示的源代码中添加一个类，并在语法分析器中注册该错误处理程序。
Listing 6 shows how to specify the error check of the returned data and dispatch the event.
清单6显示了如何指定返回数据的错误检查和发出事件。
The code in Listing 9 causes an error because it tries to use an ID that already exists in the database.
清单9中的代码导致了错误，因为它试图使用数据库中已经存在的ID。
Listing 1 shows an example of the error output generated from this on-the-fly validation.
清单1显示的是这个即时检验产生的错误输出的示例。
On the other hand, the chances are pretty good that this condition is an authoring error, like the one in Listing 1, and so the validator spits out a warning.
另一方面，这也是一个发现编辑错误的好机会，如清单1那样，因此，验证程序发出一条警告信息。
Failure to do so normally results in the error shown in listing 3.
初始化失败通常将导致清单3所示的错误。
The // ERROR comments in the listing mark the lines that fail to parse.
列表中的//ERROR注释标识了无法解析的行。
All error checking is omitted in Listing 1 for better readability, but the code you can download below demonstrates error checking as well as other SCTP socket extensions.
为了可读性更好，我们在清单1中忽略了所有的错误检查，但是这些展示错误检查机制的代码与其他SCTP套接字扩展一样都可以通过给出的链接下载到。
If you want greater precision, use ASSERT_NEAR (2.00001, 2.000011, 0.0000001) and you receive the error shown in Listing 10.
如果需要更精确的比较，应该使用ASSERT_NEAR(2.00001, 2.000011, 0.0000001)，就会得到清单10所示的错误。
Listing 10 shows error messages that you might encounter with ifxclone.
清单10展示了使用ifxclone可能会遇到的错误消息。
All these exceptions inherit from SDORuntimeException, so the minimal error handling required is shown in Listing 12.
所有这些异常都从SDORuntimeException继承，因此所需的最小错误处理如清单12中所示。
If you leave it out, you will be greeted with the nasty error message shown in Listing 5.
如果省略这一行，您将收到令人讨厌的错误消息，如清单5所示。
The error in Listing 1 is the sum of its parts.
清单1中的错误有以下几个部分。
Listing 7. Disk error from dmesg.
清单7.dmesg的磁盘错误。
You see the SQL0440N error message from Listing 2 for object TEST.v2.
您会在清单 a 中看到 TEST.v2对象的SQL0440N错误消息。
Listing 3. main error checking and display.
清单3 .main错误检查和显示。
应用推荐