由于编译时和运行时路径可能不同，有可能会产生不一致的类库需求，从而导致依赖地狱。
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.
应用推荐