The compiler generates a method for each supported remote procedure defined in the interface and properties for the arguments of the RPCs.
这个编译器为定义在接口中的每个支持的远程过程创建方法，并为RPC的参数生成属性。
Instead of having a test method per use case, we have a text file containing the expected generated code and a optional text file containing the expected compiler messages.
和每个用例有一个测试方法不同，我们有一个文本文件包含所期望的生成代码以及包含所期望编译器消息的可选文本文件。
Typically, this method is very simple and calls into a compiler or interpreter.
一般而言，该方法非常简单，就是调用编译器或解释器。
These stringent requirements ensure that the compiler can catch method invocation errors, which leads to more reliable programs.
这些严苛的要求保证了编译器可以捕捉方法调用的错误，生成的程序更可靠。
If that doesn't work, you can always try the sheer brute force method: specify the necessary compiler flags as part of your CC environment variable, or as part of the CFLAGS environment variable.
如果这样仍不行，您还可以尝试使用完全强制的方法：指定需要的编译器标记为您的CC环境变量或者是CFLAGS 环境变量的一部分。
This option generates an options file containing a list of the method signatures corresponding to the methods the JIT compiler compiled while the application ran.
该选项生成一个选项文件，其中包含一个方法签名列表，对应于JIT编译器在应用程序运行的时候编译的那些方法。
It means never thinking twice about misspelling a method name because the compiler immediately indicates the error.
这意味着，不用过多考虑方法名称的拼写错误，因为编译器能够立即指出这类错误。
Of course, if the class hierarchy changes and a second target method becomes possible, then the JIT compiler can correct the originally generated code so that the virtual invocation is performed.
当然，如果类层次结构发生变化，并且出现另外的目标方法，则JIT编译器可以更正最初生成的代码以便执行虚调用。
The equals sign before the method body tells the compiler, as well as the human reader, where the method body begins.
方法主体前面的等于号告诉编译器函数的主体从这里开始，就像我们看到的一样。
Exceptions or compiler diagnostics are passed to the log method or written directly into the scrollable errors component in the application.
异常或编译器诊断信息被传递给log方法或直接写入到应用程序中可滚动的errors组件。
The same method to calculate the factorial, this time written for the Duby compiler.
下面同样是计算阶乘的方法，这次是针对Duby编译器而写的。
How does the compiler know that the supplied argument has an iterator method?
编译器如何知道提供的参数有一个iterator方法呢？
After you set this option, the JIT compiler prints two messages for each method as it compiles the method. For example.
在设置这个选项之后，JIT编译器会在对方法进行编译时为每个方法打印两条消息。
The example shown in Listing 4 demonstrates how you might use an FXG skin as a custom component: This is the preferred method of implementation because the Flex compiler optimizes the FXG code.
清单4中的代码演示了如何将FXG皮肤用作自定义组件。这种方法是首选的实现方法，因为Flex编译器能够优化 FXG代码。
The compiler doesn't blindly compile everything though I think it can be deployed as an ahead-of-time (AOT) compiler. It kicks in whenever method execution counters trip over some threshold.
虽然我认为可以将编译器部署为AOT（ahead-of-time）编译器，但它其实并不会盲目地编译所有东西，只有当方法执行计数器超过某个阈值时它才会生效。
The compiler will try and infer the most specific type it can for the type parameters when resolving a call to a generic method. For example, with this generic method.
当解析一个泛型方法的调用时，编译器将设法推断类型参数它能达到的最具体类型。
In Scala, override has become part of the language, and forgetting it will generate a compiler error. Thus, a derived toString method should look as shown in Listing 11.
在Scala中，override已经成为语言的一部分，几乎可以忘记它会生成编译器错误。
Something else to note is that the Scala compiler doing its type inference does the right thing for the type of the "method" object returned by the if/else.
还需注意，对于 if/else返回的 “method”对象的类型，Scala编译器会进行 doestheright thing 类型推断。
It also implements the HCHandler interface (which is not a lot of work given HCHandler defines no method; it is essentially a flag for the compiler).
它还实现了HCHandler接口(如果hchandler没有定义方法，也没有多少工作量；它本质上只是编译器的一个标志)。
The compiler creates these methods that call the appropriate method in the application handler.
编译器创建这些方法，它们调用应用处理程序中的正确方法。
For the first call to a program after a cancel of that program, or for a method invocation, the compiler initializes the fields of these special registers to their initial values.
对于某个程序被取消后的第一个调用，或对于某个方法调用，编译器会初始化这些专用寄存器的字段，将它们作为初始值。
If there are two anonymous members that both provide a method, the compiler will produce an error, but only if that method is called.
如果有两个匿名成员都提供一个方法，编译器将会报错，但只在该方法被调用的情况下。
The compiler has no way of telling if you have the right integers going into the method call in the correct order since they are just three integers.
编译器无法知道在调用方法时参数传递顺序是否正确，因为它们只是三个整数而已。
Even if there are other statements between the synchronized blocks or method calls, the compiler can still perform lock coarsening.
即使在synchronized块或方法调用之间有其他语句，编译器仍然能够执行锁粗化。
As you can see, the compiler still removes the interface and still inlines each implementation of the getName() method. This is still quite optimal code.
可以看出，编译器仍然删除接口并内联 getName()方法的每个实现，这仍然是非常优化的代码。
As you have seen, the compiler ensures that the first arguments of the BeginInvoke method are the arguments of the method to be called.
正如你看到的，编译器确保BeginInvoke方法的第一个参数是被调用方法的参数。
Autoboxing: Rather than generating calls to the valueOf method in the wrapper class, the compiler generates calls to the constructor instead.
自动装箱：编译器不生成对包装器类的value Of方法的调用，而是生成对构造函数的调用。
Amidst all of the other compiler-provided methods, you should be able to find a good old public static void main (String args) method.
在所有其他编译器提供的方法之中，您应当能够找到一种优秀的旧publicstaticvoidmain (Stringargs)方法。
Generic type parameter declared with a final type bound The compiler will issue an error or warning whenever it encounters a type bound involving a final type. Consider this sample method signature.
Generictypeparameterdeclaredwithafinal typebound编译器每当遇到一个涉及final类型的类型绑定时，就会发出一个错误或者警告。
Generic type parameter declared with a final type bound The compiler will issue an error or warning whenever it encounters a type bound involving a final type. Consider this sample method signature.
Generictypeparameterdeclaredwithafinal typebound编译器每当遇到一个涉及final类型的类型绑定时，就会发出一个错误或者警告。
应用推荐