因为您配置现实世界的对象时，会得到一些编译时错误检查。
Because you're configuring real-world objects, you get some compile time error checking.
本文前面所概述的附加编译时间检查将使得这种复查值得付出努力。
The additional compile time checks outlined earlier in this article will make the review worth the effort.
一定要记住，在使用静态断言时，检查的表达式在编译时必须是可计算的。
While using static assertions, always remember that the expression being checked must be evaluable at compile time.
语法检查依赖增量编译。
静态语言的另外一个小的好处就是编译时期的额外检查。
Another small benefit of static languages is the extra checking the compiler performs.
每当您保存代码，它就在后台接受编译和语法检查。
As you save your code, it is compiled in the background and checked for syntax errors.
其优势是编译器可以做额外的错误检查。
相反，BPEL应该被视为一种经过解释的语言，尽管有一些调查检查了已编译的BPEL的潜在优势。
Instead, BPEL should be considered an interpreted language, although there have been some investigations into the possible advantages of compiled BPEL.
该编译过程牵涉到授权检查、优化，以及将语句转化为可执行格式时所需的其他一些活动。
This compilation process involves authorization checking, optimization, and other activities necessary to convert the statement into an executable form.
DB 2在编译时而不是运行时检查该变量。
DB2 checks this variable at compilation time — not at run-time.
如果EJB远程实现类要直接实现EJB远程接口，则可以在编译期间检查相关性的验证。
If the EJB remote implementation class were to implement the EJB remote interface directly, verification of dependencies could be checked at compile time.
元数据更重要的优点是编译器可以使用它来执行基本的编译时检查。
A more significant advantage of metadata is the ability for a compiler to use it to perform some basic compile-time checking.
目前为止，我们检查的所有优化都是GWT编译器所做的语言级别的优化。
So far, all of the optimizations that we have looked at were language-level optimizations made by the GWT compiler.
虽然付出了这一点成本，但可以得到非常好的性能，编译时类型检查，以及一个非常高级的语言。
For the trouble, you get rock-solid performance, compile-time type checking, and a very high-level language.
当然，还会失去编译时检查的安全保障。
Of course, you also give up the safety net of the compile-time type checking.
检查在编译过程中出现的错误。
Scala甚至使得把null作为第二个参数传给构造函数变得很困难；它不会再编译时做类型检查。
Scala even makes it difficult to pass null as the second parameter to the constructor; it won't type check when you compile it.
它不会再编译时做类型检查。
mwarn-framesize=framesize和 -mwarn-dynamicstack：这些选项会引起在编译时检查函数是否超过给定的堆栈帧（stack frame）大小或使用动态调整的堆栈帧。
mwarn-framesize=framesize and -mwarn-dynamicstack: These options cause a compile-time check whether a function exceeds a given stack frame size or uses dynamically sized stack frames.
同样，对“外露”类型参数的instance of检查将在编译时产生“unchecked”警告，而且检查将不会如期在运行时进行。
Similarly, instanceof checks on naked type parameters will result in an "unchecked" warning at compile time and the check will not occur as expected at runtime.
warn_unused _ result让编译器检查所有调用者是否都检查函数的结果。
Warn_unused_result forces the compiler to check that all callers check the result of the function.
程序语言有“语法规则”，由其决定了程序是否构造正确。 编译器检查程序是否违反了语法规则，并且在规则被破坏的时候产生语法错误报告。
Programming languages have a set of syntax rules that determine whether a program is
用于文档编制、编译器检查和代码分析的工具可以使用这些额外信息。
This additional information is used by tools for the purposes of documentation, compiler checking, and code analysis.
如果它没有编译和链接，请仔细检查这些阶段，并确保早先没有出现会引起稍后出错的警告。
If it didn't compile and link, double-check the stages and ensure that there were no early warnings causing errors later on.
基于注释属性的切入点有某些好处，特别是对于编译时检查和静态选择的效率。
There are certain advantages to annotation properties-based pointcuts, especially for compile-time checks and efficiency of static selection.
检查系统时钟；更重要的是，要检查编译树中文件的日期、系统中其他文件的日期以及系统的时钟。
Check your clock; more importantly, look at the dates of files in your build tree, and other files on your system, and your clock.
通过静态类型，编译器可以检查参数和变量的值或针对一个给定操作所允许的返回值。
With static typing, the compiler can check the values of arguments, variables, or return values against values allowed for a given operation.
在生成和运行可执行程序时，始终检查是否存在编译错误。
Always check for compilation errors before you generate and run an executable program.
查询编译器在检查字符比较操作时使用该信息，以决定如何执行操作。
The query compiler uses this information while checking any character comparison operations, to decide how to evaluate the operations.
一般来说，元数据的好处分为三类：文档编制、编译器检查和代码分析。
In general, metadata's benefits fall into three categories: documentation, compiler checking, and code analysis.
应用推荐