An error was reported when he tried to write data to the file for the first time.
当他第一次尝试把数据写入文档时，报告说有错。
It includes job name, job execution times, number of rows processed, error or success status, time started, and time completed, which are all described in sequence.
它包括作业名称、作业执行次数、处理的行数、错误或成功状态、开始时间及完成时间，这些都是按顺序描述的。
The trial and error process can be a huge waste of time.
尝试和错误恶性循环的过程是很浪费时间的。
If no response is received after the specified time, an error is produced.
如果在指定时间之后没有收到响应，将产生错误。
It also evaluates your language constraints in real time and outputs error messages.
它还可以实时评估你的语言约束，并输出错误消息。
It finds one syntax error at a time, so you have to be a little patient to do it, but you can check that the syntax is right.
它一次会找到一个语法错误，所以你们必须要有点耐心，但是你们可以检查出语法是否正确。
Because you're configuring real-world objects, you get some compile time error checking.
因为您配置现实世界的对象时，会得到一些编译时错误检查。
You can see the detailed error information at run time and debug it by reviewing the system log and event log.
您可以看到运行时的详细错误信息，并通过查看系统日志和事件日志进行调试。
With this implementation, you get neat compile time error messages.
如果使用此实现，您会得到相应的编译时错误消息。
Instead, the error signaled at run time would be a null-pointer exception instead of a class-cast exception.
相反，在运行时发出的错误将会是一个空指针异常而不是类强制转换异常。
Verifying that the deployment of such an application is successful is time consuming and error prone.
这会让我们耗费大量时间来验证这样的应用程序部署是否成功，并且很容易产生错误。
You will save a great deal of time if you leave error reporting enabled.
如果启动了错误报告，会节约许多时间。
Repeated opening and closing of Ambulant from the command-line interface (CLI) destroys the error buffer each time.
通过命令行界面(CLI)重复打开和关闭ambulant每次会破坏错误缓冲。
Ruby gives you an error at run time because Ruby supports dynamic typing.
而Ruby则是在运行时给出错误消息，因为Ruby支持动态类型。
Any attempt to perform a string comparison on an employee ID will then fail with a type error at query run time.
在查询运行时，尝试在雇员ID上执行字符串比较将遭到失败，并产生一个类型错误。
They needed a stronger crystal, but the process of trial and error takes a long time.
他们需要一个更强的晶体，但是试错的过程耗费了他们很长的一段时间。
For example, at the beginning of a project, you may be testing to set quantitative baselines (such as time, error rates, and satisfaction) for comparison to later tests of your revised site.
举例来说，项目刚刚起步，你可以对定量的指标(如时间，错误率和满意度)进行测试，为日后修改网站提供参照。
The type-safety feature will provide for much earlier error detection at compile time, rather than at run time with the standard JPQL constructs.
类型安全功能将提供在编译时的早期错误检测，而不是使用标准JPQL 构建时的运行时检测。
They are proven to produce the low-error estimate and incur almost no run-time overhead.
它们被证明可以产生低误差的估计，并且几乎不占用运行时开销。
This incompatibility between platforms is particularly dangerous as it might cause programs to return wrong results rather than causing a compile-time error.
不同平台之间的不兼容性尤其危险，因为它可能会导致程序返回错误结果，而不是编译时错误。
Listing 2 shows a piece of code that results in a compile-time error because the copy constructor is private.
清单2显示了产生编译时错误的代码部分，因为该拷贝构造函数是私有的。
If you get error messages the first time that you save (as I did), hover your cursor over the error message to get more details about the problem.
如果您在首次保存时出现了错误消息(就像我一样)，可以将鼠标移到这个错误消息上，从而获取关于这个问题的详细情况。
UML modeling is a valuable technique by itself, but manually synchronizing models and code is error-prone and time consuming.
UML建模是有价值的技术，但人工地将模型和代码同步是容易出错且消耗时间的。
Figure 6 shows the same error as in Figure 5, but this time the error-handling code gives a much better picture of what happened to the user or programmer.
图6给出了与图5相同的错误，但是这一次错误处理代码向用户或程序员更好地说明了究竟发生了什么。
Collecting data from end users, especially when primarily paper-based methods are used, is often time-consuming and error-prone.
从终端用户收集数据，尤其是当最初使用基于纸张的方法时，通常是费时且易错的。
Unfortunately, in many organisations this critical process is still rather time-consuming and error-prone.
不幸的是，在许多组织中这项关键的流程还是费时并容易出错的。
But this would be tedious, error-prone, and time-consuming, and it would require a highly skilled developer to ensure that the architectural decisions were implemented correctly.
但是这样做非常冗杂、易出错、费时间、并且需要一个高水平的开发人员确保体系结构决定能够正确的被实现。
This can be done manually, but it is exceedingly time consuming and error prone.
这可以手工完成，但是会耗费很长时间，而且很容易出错。
Comparing tuples of unequal lengths results in a compile-time error.
比较不同长度的元组会产生编译时错误。
However, refining class models with textual constraints is a time-consuming and error-prone task.
然而，用文本约束细化类模型是耗费时间并且易于出错的任务。
应用推荐