在生成和运行可执行程序时，始终检查是否存在编译错误。
Always check for compilation errors before you generate and run an executable program.
第一种方法要求程序在在进行每一个重大操作之后，检查错误。
The first method requires the program to check for error conditions after every non-trivial action.
带启用断言检查运行程序产生下面的错误报告
Running the program with assertion checking enabled produces the following error report
程序语言有“语法规则”，由其决定了程序是否构造正确。 编译器检查程序是否违反了语法规则，并且在规则被破坏的时候产生语法错误报告。
Programming languages have a set of syntax rules that determine whether a program is
因为这是打算用于通用目的而不是只被一小群人使用的实用程序，所以我们进行大量的错误检查以使它尽可能的健壮。
Since this is a utility meant for general purpose use, not just by a small group of people, we do a lot of error-checking to make it as robust as possible.
某些派别的信徒支持使用异常来检查参数和其他的前置条件，使用错误编码来报告程序中出错的处理。
Some disciples espouse using exceptions to check parameters and other preconditions, and error codes to report processing errors within the function.
如果一个程序提供详细的错误输出而且表现正常，那么不使用任何特权来运行这个程序，然后检查错误消息，看看它缺少哪些特权。
If a program were verbose and well behaved, it might be possible to simply run the program without privilege and have it complain about which privileges it lacks.
因为必须要在源代码中消除错误，所以，应该有一个精通程序的人来检查错误，并知道这些错误的根本原因。
Someone who knows the program well should examine the bugs and understand their root causes, since bugs must be eliminated at their source.
类型检查器应该能帮助程序员从这些类型的错误中恢复，但对于静态字段而言，类型系统实际上会使程序员更迷惑。
The type checker is supposed to help a programmer recover from exactly these sorts of mistakes, but in the case of static fields, the type system could actually help to confuse the programmer.
找到错过的程序错误的模式是检查测试覆盖的一个重要技术。
Finding patterns of missing bugs is an important technique to verifying test coverage.
一般，通常检查应用程序或中间件中各种数据结构的状态即可确定该状态的错误因素。
They are generally diagnosed by examining the state of various data structures in the application or middleware to determine if some aspect of that state is incorrect.
示例程序在事件发生数据中检查错误格式，判断select()调用是否返回了错误。
The sample program checks for the error format in the event occurrence data if the select() call returned an error.
程序员只需在提交大型机编译前对程序执行本地语法检查，错误就将在WebSphereDeveloperfor zSeries Problems视图中列出。
The programmer just has to perform local syntax checking for the program before submitting a mainframe compilation, and the errors will be listed in the WebSphere Developer for zSeries Problems view.
我们还可以检查用于 GetCustomerDetails调用的错误处理程序，指明可能需要区别对待 notFound 错误和transientError 错误（图13）。
You can also examine the fault handlers for the GetCustomerDetails invoke, noting that notFound faults and transientError faults are potentially treated differently (Figure 13).
然后，当您运行这个测试过的程序时，Purify就会通过您的程序详细检查内存访问和操控，鉴定将要发生的内存错误。
Then, when you run the instrumented program, Purify scrutinizes memory accesses and manipulations by your program and identifies memory errors that are about to happen.
虽然Soundex和Metaphone算法都很好地解决了语音模糊的匹配问题，但是如果不能纠正打字错误，那么拼写检查应用程序是不完整的。
While both Soundex and Metaphone algorithms solve phonetic fuzzy matching very well, no spell checking application is complete without typo correction.
在测试应用程序时存在稳定的回归测试时，引入类似Purify的运行时错误检查工具就是比较明智的事情。
When a solid regression suite is present for testing the application, incorporating a runtime error detection tool such as Purify in it is a smart thing to do.
比如mysqlcheck - uroot- pawtDB 2没有直接匹配的程序检查表错误。
For example, mysqlcheck -u root -p awt DB2 does not have a direct matching for table corruption check per se.
“磁盘扫描程序”试图修正前面的错误时出错。请对这个驱动器运行完全检查。
An error occurred while ScanDisk was attempting to correct the previous error. Complete a thorough check of this drive.
识别语义错误是十分微妙的，它要求你进行反向的工作检查程序的输出，并且查明它在做什么。
Identifying semantic errors can be tricky because it requires you to work backward by looking at the output of the program and trying to figure out what it is doing.
这段代码检查ISBN对象是否不相同。如果不同的话，停止程序的执行，并将控制转移给处理这种错误的处理代码。
In this code we check whether the ISBNs differ. If so, we discontinue execution and transfer control to a handler that will know how to handle this error.
使用不需检查运行时异常来报告严重的、无法预期的错误，这可能指出程序逻辑中的错误。
Use unchecked, run-time exceptions to report serious unexpected errors that may indicate an error in the program's logic.
如果他选择加入更多的错误检查，额外程序可以很容易地添加到提供的代码。
If one chooses to add more error checking, additional procedures can easily be added to the provided code.
如果发现错误，将其纠正，再次运行检查程序。
If any errors are found, correct the errors and run the check again.
该检查模块能够正确找出已编写程序的语法和一些简单的逻辑错误，对后续开发具有指导意义。
This checking module can correctly find syntax errors and some simple logical errors of the diagram program, which provides guidance for the further development.
使用需检查异常来报告可能发生但是在正常程序操作中很难发生的错误。
Use checked exceptions to report errors that may occur, however rarely, under normal program operation.
把大的程序切分成小块的函数，就自然为我们调试建立了一个个的检查点。在不工作的函数里面，有几种导致错误的可能。
Breaking a large program into smaller functions creates natural checkpoints for debugging. If a function is not working, there are three possibilities to consider.
检查打字问题最简单的方式是使用拼写检查程序，但检查语法错误就繁杂得多。
The easiest way for checking for typos is to use a spellchecker, but checking for grammar mistakes is a lot trickier.
检查打字问题最简单的方式是使用拼写检查程序，但检查语法错误就繁杂得多。
Thee easiest way for checking for typos is to use a spellchecker, but checking for grammar mistakes is a lot trickier.
检查程序向用户输出的文本或信息中是否存在拼写或语法错误。
Are there spelling or grammatical errors in any text that is printed or displayed by the program?
应用推荐