降低客户端编码错误。
虽然这不会造成严重错误，但这是一个编码错误。
That won't cause a fatal PHP error, but it is a coding error!
尽早测试的作用不仅仅是防止编码错误。
编码错误是由程序员在实现需求时的错误而引起的。
Coding bugs result from programmer errors in implementing the requirements.
这有时是有用的，但最常见的是编码错误。
This is sometimes useful, but is most often a coding mistake.
出现了一个编码错误。
编码错误会导致不正确的程序行为(偏离需求的行为)。
Coding bugs cause improper program behavior (behavior deviating from the requirements).
我们已经将编码错误定义成程序员在实现需求时产生的错误。
We have defined coding bugs as errors by the programmer in implementing the requirements.
如果您发现了一个XML编码错误，您将看到一个输出错误。
If you happened to make an XML coding error, you will see an error output instead.
如果发现了一个XML编码错误，您将看到如图6所示的消息框。
If you happened to make an XML coding error, your message box will show an error similar to Figure 6.
有三种基本类型的错误：编码错误、文档错误和需求错误。
Bugs come in three basic varieties: coding bugs, documentation bugs, and requirement bugs.
然而，在现实世界中，我们常常见到由缺少方便的函数而导致的编码错误。
In the real world, however, we have seen very frequent coding errors caused by this lack of convenient functions.
本机代码可能尝试访问具有无效输入(如过时的本地引用)或编码错误的对象。
Native code may attempt to access an object that has invalid input (such as a stale local reference) or that is coded incorrectly.
补充编码标准几乎能够消除某些类型的编码错误，如关于放置花括号或注释的错误。
Beefing up coding standards can all but eliminate some types of coding errors, like bugs related to brace or comment placement.
URI的字符串表示形式容易导致分析和编码错误，并且可造成安全漏洞。
A string representation of a uri is prone to parsing and encoding errors, and can lead to security vulnerabilities.
NET应用程序并不只是为了避免常见的编码错误，例如未验证使用者输入。
NET application involves more than avoiding common coding pitfalls such as not validating user input.
如果有报表频繁丢失或编码错误，那么有个方法，就是劝诫雇员工作得久一些或更细心点。
If there's a report that frequently gets lost, or miscoded, one approach is to exhort employees to put in longer hours, or to be more careful.
在组评审中，您能够摆脱那些琐碎的和令人为难的编码错误和矛盾的困扰，将精力集中到设计问题上面。
In group reviews, you can focus on design issues without being side-tracked by trivial and embarrassing coding errors and inconsistencies.
例如一个这样的表单，其中包含一个编码错误的按钮，每当按这个按钮时，都会导致一个可重复的崩溃。
One example is a form that includes a badly coded button that always results in a crash when pressed.
然而，在现实世界中，我们看到由于缺乏便利的函数导致频繁的编码错误占了80%的情况，这样做的确有意义。
In the real world, however, we have seen frequent coding errors caused by the lack of a convenient function to cover the 80% of cases where it does make sense.
因为变量的名字既描述了变量的用途又描述了其数据类型，这样你就不太可能出数据类型匹配上的编码错误。
Because the name of a variable describes both the use of a variable and its data type, you are much less likely to make coding errors involving mismatched data types.
不幸的是，需求错误和文档错误不在本文范围之内，因此，我们只好只讨论如何“检测”、“解决”和“修复”编码错误了。
Unfortunately requirement and documentation bugs are outside the scope of what we can do here, so we'll have to limit ourselves to "detecting," "solving," and "fixing" coding bugs.
如果你正在考虑这样做只是为了防止编码错误(打错子程序)或允许多个子程序具有相同标识符，那么我会说你是在浪费你的时间。
If you are considering doing it only to prevent coding mistakes (calling the wrong subroutine) or to allow multiple subroutines with the same identifier, then I would say you were wasting your time.
我插话道，“返回一个错误编码不可以吗？”
不幸的是，错误和糟糕的编码实践不仅不太专业，而且可能减缓应用程序的速度。
Unfortunately, errors and bad coding practices are not only unprofessional but can also slow down your application.
某些派别的信徒支持使用异常来检查参数和其他的前置条件，使用错误编码来报告程序中出错的处理。
Some disciples espouse using exceptions to check parameters and other preconditions, and error codes to report processing errors within the function.
反过来，这又可以帮助开发团队检测(大多数情况下是校正)编码阶段的错误。
This, in turn, helps development teams detect - and, in most cases, correct - problems during the coding phase.
通过告知这个构建的错误，开发者们能够调查并识别来自于他们编码的错误。
By including the build failures, developers can investigate and identify faults that stem from their code.
如果不是一个严重的错误，我就可以使用一个错误编码作为返回值吗？
So if it wasn't such a severe error, I could just bail out with an error code?
如果不是一个严重的错误，我就可以使用一个错误编码作为返回值吗？
So if it wasn't such a severe error, I could just bail out with an error code?
应用推荐