Comparing tuples of unequal lengths results in a compile-time error.
比较不同长度的元组会产生编译时错误。
Using any of the other three forms of cast in this case would result in 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显示了产生编译时错误的代码部分，因为该拷贝构造函数是私有的。
You will have a compile-time error something like: "The nested type Person cannot hide an enclosing type".
否则将会导致一个编译时间错误，如 “该嵌套类型Person无法隐藏封闭类型”。
In fast mode, a compile-time error will be generated if you attempt to assign a value to a read-only identifier.
在快速模式中，如果尝试为只读标识符赋值，将生成编译时错误。
If there is no default constructor, then there is a compile-time error: the object must be given an explicit initializer.
如果没有默认构造函数，那么将会出现编译时错误：必须要给对象指定显式的初始化式。
If client code tries to instantiate your class by using a type that is not allowed by a constraint, the result is a compile-time error.
如果客户端代码尝试使用某个约束所不允许的类型来实例化类，则会产生编译时错误。
So if you misspelled "secret" in the above example, or tried to call a method on it that did not exist, you would get a compile-time error.
因此如果在上例中拼错了“secret”，或尝试调用根本不存在的方法，那么将出现编译时错误。
This incompatibility between platforms is particularly dangerous as it might cause programs to return wrong results rather than causing a compile-time error.
不同平台之间的不兼容性尤其危险，因为它可能会导致程序返回错误结果，而不是编译时错误。
It is a compile-time error for a single ElementType constant to appear more than once in a Target annotation. For example, the following meta-annotation is illegal.
对于一个元素类型常量出现多余一个的目标注释是编译错误的。例如下面的例子是不合法的。
With this implementation, you get neat compile time error messages.
如果使用此实现，您会得到相应的编译时错误消息。
On top of that, we introduced the new Codan static analysis framework as optional component to provide semantic error reports ahead of compile time.
在此基础之上，我们引入新的Codan静态分析框架作为可选组件，在编译之前提供语义错误报告。
Because you're configuring real-world objects, you get some compile time error checking.
因为您配置现实世界的对象时，会得到一些编译时错误检查。
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 构建时的运行时检测。
Creating a custom plug-in for Perl or Python code that lets you compile sources from within the editor, and then positions the cursor on the error may help save a lot of development time.
可以为Perl或Python代码创建用于从编辑器内编译源代码的定制插件，还可以把光标放在有错误的地方，这有助于节省大量开发时间。
A dynamic object is assumed at compile time to support any operation, and only at runtime will you get an error if it wasn't so.
在编译时，会假设动态对象支持任何操作，而如果它不支持某个操作，则只有到运行时才能得到错误。
The ideal time to catch an error is at compile time, before you even try to run the program.
最良捕获错误信息的时机应该是在编译时，在运行程序之前。
In order for the command-line compiler to find the runtime error with -f, you must compile the program with all the same command-line parameters you used the first time you compiled it.
为了命令行编译器能用- F选项查找运行期间错误，你必须传递与第一次编译时相同的指令列表。
For example, if no class Foo exists, an error will be generated at compile time for the first version.
例如，如果没有一流的美孚存在，一个错误会在编译时产生的第一个版本。
Implicit conversions succeed only when the process loses no data; otherwise they fail and generate a compile or run-time error.
隐含转换只在处理序不遗失资料时才会成功，否则会失败并且产生编译或执行阶段错误。
A failed conversion here will result in a compile time error.
在这里失败的转换会导致编译时期错误。
If you attempt to use an undeclared variable name, an error occurs at compile time.
如果您尝试使用未宣告的变数名称，会发生编译时期错误。
If you attempt to use an undeclared variable name, an error occurs at compile time.
如果您尝试使用未宣告的变数名称，会发生编译时期错误。
应用推荐