它可以在编译时执行给定的操作。
静态类型语言在编译时实施类型。
静态JSP包含在编译时解析。
想要调用的方法必须在编译时存在。
The method that you want to invoke must exist at compile time.
它是否会干扰编译时优化呢？
不过，您仍然可以享用编译时的益处。
You can, however, take advantage of the compile-time benefits.
它不会再编译时做类型检查。
当然，还会失去编译时检查的安全保障。
Of course, you also give up the safety net of the compile-time type checking.
简单来说，泛型为集合提供了编译时类型安全。
Simply put, generics provide compile-time type safety for collections.
定制编译的好处、过程和编译时的一些考虑因素
The benefits of custom compilation, the procedure, and some considerations at compile time
比较不同长度的元组会产生编译时错误。
Comparing tuples of unequal lengths results in a compile-time error.
如果使用此实现，您会得到相应的编译时错误消息。
With this implementation, you get neat compile time error messages.
在这个示例中，我要捕获源代码编译时的错误条件。
In this example, I've attempted to capture an error condition when compiling source code.
可以使用这个字段指定将记录编译时警告的文件位置。
You can use this field to specify the file location that will record the compile-time warnings.
问题是，这行代码是在编译时绑定的，这就太静态了。
The problem is that this line of code gets bound at compile time, and that's too static.
通常需要在编译时完成尽可能多的工作以获得更好的性能。
Usually you want to do as much work as possible at compile time for performance.
服务程序可以在编译时被绑定到Handlder程序。
This service program can be bound to the handler program at compile time.
因此，不能复制在编译时根本不知道是什么类的类型引用。
OK, so you can't copy a reference to a type whose class is totally unknown at compile time.
在静态语言中，编译器在编译时直接将调用绑定到实现。
You've seen that with static languages, the compiler directly binds an invocation to an implementation at compile time.
函数注释会在编译时将表述与函数的某些部分(比如参数)相关联。
Function annotations associate expressions with parts of a function, such as parameters, 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.
集中于1.6版的主要焦点是改进编译时和运行时的性能。
The primary focus for 1.6 is improving performance during compile-time and runtime.
因为代码可以在任何环境中执行，所以类文件可能与代码编译时不同。
Because the code can execute in any environment, the class files might not be the same as when the code was compiled.
不同之处在于重新编译时，在这个过程中您会重用先前的预处理程序。
It's the recompilation, where you are reusing previous preprocessor passes, that will make a difference.
因为您配置现实世界的对象时，会得到一些编译时错误检查。
Because you're configuring real-world objects, you get some compile time error checking.
至于成功编译的代码，您需要将JAR添加到编译时类路径上。
For the code to compile successfully, you need to add the JARs to the compile time classpath.
清单2显示了产生编译时错误的代码部分，因为该拷贝构造函数是私有的。
Listing 2 shows a piece of code that results in a compile-time error because the copy constructor is private.
认担动作很像AOP，只不过它是发生在运行时，而不是编译时。
Contributed actions are very like AOP, except that they happen at run-time not compile time.
基本的菜单仍然在编译时确定——运行时仅仅改变额外的可选项。
The basic menus are still decided at compile time — runtime changes simply modify the optional extras.
传递给该参数的任何函数都必须满足这个签名，否则将得到一个编译时错误。
Any function passed in to this parameter must satisfy this signature, or you will get a compiler error.
应用推荐