由于编译时和运行时路径可能不同，有可能会产生不一致的类库需求，从而导致依赖地狱。
Since the compile time and runtime paths may be different, it's possible to have inconsistent library requirements leading to dependency hell.
历史应用程序(即很过时的遗留代码)有时会直接引用这些全局变量，但会在编译过程中产生错误，因为它们的声明并不一致。
Historical applications (that is, horribly outdated legacy code) sometimes refer to these directly, but produce errors during compilation because they're declared inconsistently.
代码的运行结果与预期一致，没有编译错误，最重要的是这段代码的可读性非常好：其意图是非常清晰的。
The code runs as expected, no compiler errors or issues and - most usefully - the code is self-documenting: the intention is clear.
本文假定您熟悉内核构建过程，并了解内核编译所带来的发行版间的不一致性。
This article assumes familiarity with the kernel build process, as well as experience with the inconsistencies among distributions when it comes to kernel compilation.
编译器同时也会确保EndInvoke返回值类型和委托返回类型一致（在我们的例子中，这个类型是int）。
There also the compiler ensures that the return value of EndInvoke is the same as the return value of the delegate type (this type is an int in our example).
好消息是，开发者几乎总会发现，不同的Linux发行版本中代码编译是一致的，POWER版Linux也不例外。
The good news is, developers nearly always find code builds compatible across Linux distributions, and Linux on POWER is no exception.
编译器验证给定类型的对象的使用方式是否与该类型的定义一致，描述这一过程的术语。
Term used to describe the process by which the compiler verifies that the way objects of a given type are used is consistent with the definition of that type.
找到一种代码风格不被编译器或解释器重视的微小部分应该至始至终的保持一致。
Have a code style. All the little things that the compiler or interpreter doesn't care about should be done the same way throughout a project.
同样，这个前人口或背部修补确保编译器生成的代码是由编译器调用一致的编译器调用。
Again, this pre-population or back patching ensures compiler generated code is consistent from compiler invocation to compiler invocation.
当你在命令行中使用-V选项时，编译器会在可执行文件的末尾附加与Turbo Debugger5.0一致的外部调试信息。
When you specify the -V option on the command line, the compiler appends Turbo Debugger 5.0-compatible external debug information at the end of the executable file.
需注意的是，假如两个函数的名称与参数列表均一致然而返回类型不同的话，这就是个编译错误。
You should note that two functions with the same name and parameter list, but different return types, generate a compiler error.
以下各节解释预编译头的一致性要求。
The following sections explain the consistency requirements for precompiled headers.
如果编译器检测到不一致性，它将发出警告并在其可能出现的地方标识该不一致性。
If the compiler detects an inconsistency, it issues a warning and identifies the inconsistency where possible.
如果编译器检测到不一致性，它将发出警告并在其可能出现的地方标识该不一致性。
If the compiler detects an inconsistency, it issues a warning and identifies the inconsistency where possible.
应用推荐