您要查找的是不是：
- compile time diagnostics 编译时诊断
- The default base name is specified at compile time. 编译时已经指定了默认的基本文件名。
- Tag remapping occurs at compile time. 在编译时重新映射标记。
- These are configurable at runtime or compile time. 它们在运行时或者编译时是可配置的。
- Most diagnostics issued by the client are logged in a specified log file. The log file name is specified at compile time, but may be overridden on the command line. 通常情况下诊断信息都记录到指定好的记录文件中。而这个文件的名称在编译时可以指定,但其它命令行操作也可以不使用这个文件。
- In fact static method calls are resolved at compile time. 实际上，静态方法的调用在编译时解决。
- Constants are values which are known at compile time and do not change. 常数是在编译时已知并保持不变的值。
- There is no need to write code to test for the correct data type, because it is enforced at compile time. 不需要编写代码来检测数据类型是否正确,因为会在编译时强制使用正确的数据类型。
- SQLJ can perform syntactic and semantic checking on the code, using database connections at compile time. SQLJ可以通过在编译时使用数据库连接,对代码执行语法和语义上的检查。
- They cause parts of your code to be included or excluded at compile time depending on certain conditions. 条件编译语句可让代码的各个部分在编译时根据具体的条件,或包括在编译之内,或排除在编译之外。
- This helps make sure that the plan guide will be matched to the query at compile time. 参数使用。这有助于确保计划指南在编译时与查询匹配。
- Type existence is checked at compile time rather than read time, reducing possibility for error. 时,将在编译时而不是读取时检查类型是否存在,这可以减少出错的可能性。
- If you attempt to use an undeclared variable name, an error occurs at compile time. 试图使用未声明的变量名将发生编译时错误。
- You can make the reference either at compile time (early binding) or at run time. 您可以在编译时(事先绑定)或在运行时进行引用。
- A constant expression is an expression that can be fully evaluated at compile time. 常数表达式是在编译时可被完全计算的表达式。
- Updating the status bar command prompt for commands whose IDs are not known at compile time. 为ID在编译时未知的命令更新状态栏命令提示。
- Is not resolved at compile time, so you can use it as the return value of a property or method. 因此可以将它用作属性或方法的返回值。
- When you do not know at compile time what data type the variable might point to. 当您在编译时不知道变量可能指向哪种数据类型时,请使用。
- The selection of implementation is performed at compile time, so there is no runtime overhead. 具体实现的选择是在编译期执行，所以没有运行期的开销。
- At runtime or compile time, depending on your AOP framework, cross-cutting code is injected at the specified pointcuts. 在运行时或编译时，依据你的AOP架构，横切代码注入到特定的点切。
