如何查明谁在传递错误的参数值？
给我的某个函数传递的是错误的参数值。
The wrong parameter value is being passed to one of my functions.
但是，如果你给它错误的参数，你可以测试失败！
But if you give it bad parameters, you can test that it fails!
这极为简单，使用错误的参数类型调用构造函数或方法时，会引发异常。
This is extremely simplistic and leads to an exception being thrown when a constructor or method is called with the wrong argument types.
参数错误辨识的目的是找出错误的参数，参数错误估计的目标则是给错误的参数提供一个正确的估计值。
The aim of parameter errors identification is to find the wrong parameter, the goal of parameter errors estimation is to provide a correct estimation value for the wrong parameter.
在研究者建立完一个问题的模型之后，他们根据Patera帮助开发的分析技术，选择能够成功最小化错误的参数。
As the researchers build a problem model, they select parameters that will successively minimize error, according to analytic techniques Patera helped developed.
常常可以发现bug的原因是调用者发送了类型错误的参数或数量错误的参数，或者实际参数和形式参数的次序不匹配。
Often, you can trace the origin of a bug back to a caller that's sending the wrong type of argument, the wrong number of arguments, or a mismatch between the order of actual and formal arguments.
该回调函数的参数包括一个事务句柄和一个错误对象。
The arguments to this callback function include a transaction handle and an error object.
如果错误数量超过了由一个特定参数指定的阈值，那么将停止处理。
If the number of errors exceeds a threshold specified by a specific parameter, processing is stopped.
一般情况下，DOM实现必须检验操作的正确性，并在应用程序传递错误参数或者执行非法操作时抛出异常。
Normally, a DOM implementation must verify the correctness of operations and throw an exception if an application passes the wrong parameters or performs an illegal operation.
该函数将错误代码和一个预分配的缓冲区作为参数。
It takes the error code and a pre-allocated buffer as its parameters.
当开发odbc应用程序时，常见的错误常常发生在为API提供参数值时。
When developing ODBC applications, common mistakes are often made while giving parameter values for API's.
它们的含义由它们在参数列表里的位置隐式确定，所以其排序中的任何错误都会悄悄改变其含义。
Their meaning is determined implicitly by their position in the argument list, and so any mistake in their ordering silently changes their meaning.
实际上，上面的代码并没有多少工作：当SPE试图检索自己的参数时，会得到一个总线错误。
In fact, the code above won't quite work: it gets a bus error when the SPE tries to retrieve its arguments.
如果不给出参数，则它会显示所有定义的错误消息。
bar脚本代码使您能自动操作并修改BAR参数，从而减少人工参与及错误的总量。
The BAR's scripting code allows you to automate and modify the BAR's parameters, reducing the amount of manual intervention and errors.
某些派别的信徒支持使用异常来检查参数和其他的前置条件，使用错误编码来报告程序中出错的处理。
Some disciples espouse using exceptions to check parameters and other preconditions, and error codes to report processing errors within the function.
如果遇到SQL 0964c错误，就需要增加数据库日志文件参数的值。
If you encounter the SQL0964C error, you will need to increase the values of your database log file parameters.
除了少数例外情况，在可写通道或异常通道中选择这两个参数是错误的。
With few exceptions, it's a mistake to select on writeable or exceptional channels.
如果错误设置这个参数(例如，将一个空数据的初始加载设置为DELTA)，则可能会导致一些错误，从而导致执行中断。
An incorrect setting for this parameter (for example, setting the initial loading of an empty database to DELTA), can result in a number of errors that can cause execution to abort.
MDM_EC参数组包含用于错误控制和报告的参数。
The MDM_EC parameter set consists of parameters that are used for error control and reporting.
在开始调整任何当前设置之前，检查两个常常导致SQL 1042错误的配置参数ASLHEAPSZ和QUERY_HEAP _ SZ。
Before you start adjusting any of the current Settings, check the two most common configuration parameters ASLHEAPSZ and QUERY_HEAP_SZ that are usually involved in a SQL1042 error.
当使用错误的输入参数类型来调用存储过程时，将返回下列错误。
When the procedures are called with wrong input parameter types, this error is returned.
另一个常见错误是误解了NoCache参数的用法。
Another common error is to misunderstand the use of the NoCache argument.
如果遗漏了必需的参数，则setAccessibleValues()语法会强制产生一个错误。
The setAccessibleValues() syntax forces an error if required arguments are omitted.
这种限制实际上是与XSLTv1的少数不兼容性之一，但这很好，因为能够消除参数名称中的键入错误。
This limitation is actually one of the few incompatibilities with XSLT v1, but it's a good one because it stops typing mistakes in parameter names.
使用基于OLAP的包时，使用值表达式作为tuple函数的参数的报告将生成以下错误消息。
When using OLAP based packages, reports which use value expressions as parameters to the tuple function produce the following error.
调用str . join时提示了错误的TypeError信息：隐藏的“self”参数没有计算在内。
Wrong TypeError message when invoking "str.join" : implicit parameter 'self' not counted.
但是这样做通常是一个严重的错误，因为即使它们返回的值以这种方式使用，与列表相关的函数仍然修改它们的原始参数。
Doing so would almost always be a serious mistake, however, because even when their return values are used in this way, list-related functions still modify their original argument.
但是他们并不知道这些参数各自代表什么，于是又为这些参数添加更完善的错误检查和“帮助”描述。
They don't know what the arguments are supposed to be, so add better error checking and "help" descriptions for the arguments.
应用推荐