静态类型语言在编译时实施类型。
静态JSP包含在编译时解析。
它是否会干扰编译时优化呢？
定制编译的好处、过程和编译时的一些考虑因素
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.
因此，不能复制在编译时根本不知道是什么类的类型引用。
OK, so you can't copy a reference to a type whose class is totally unknown at compile time.
当您触发一个GWT编译时，将显示一个如图1所示的对话框。
When you trigger a GWT compile, it will bring up the dialog shown in Figure 1.
比如，最近有人问我如何输出在编译时不知道数量的点(句点)。
For example, recently I was asked how to print a certain number of dots (periods) where the number to print wasn't known 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.
因为代码可以在任何环境中执行，所以类文件可能与代码编译时不同。
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.
在编译时，可以使用GCC提供的一个内置函数判断一个值是否是常量。
GCC provides a built-in function that you can use to determine whether a value is a constant at compile-time.
至于成功编译的代码，您需要将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.
对于Psyco，有“运行时”、“编译时”和“虚拟时”变量。
For Psyco, there are "run-time," "compile-time" and "virtual-time" variables.
元数据可以用于创建文档，跟踪代码中的依赖性，甚至执行基本编译时检查。
Metadata can be used to create documentation, to track down dependencies in code, and even to perform rudimentary compile-time checking.
所以，编译时不建议使用针对特定体系结构的标记，比如-mpower。
Therefore, it is not recommended to compile with architecture-specific flags, such as -mpower.
基于注释属性的切入点有某些好处，特别是对于编译时检查和静态选择的效率。
There are certain advantages to annotation properties-based pointcuts, especially for compile-time checks and efficiency of static selection.
SQLJ可以通过在编译时使用数据库连接，对代码执行语法和语义上的检查。
SQLJ can perform syntactic and semantic checking on the code, using database connections at compile time.
SQLJ可以通过在编译时使用数据库连接，对代码执行语法和语义上的检查。
SQLJ can perform syntactic and semantic checking on the code, using database connections at compile time.
应用推荐