Set the time machine to 1988. The C language has not yet been standardized. Everybody had their own libraries for doing stuff, and some of them even pretended to be compatible with each other. The Microsoft C compiler, for example, came with a bunch of functions like unlink
and stat
to provide sort-of compatibility with Unix-sort-of source code.
And then the C standard was ratified in 1989. Now things got interesting, because those functions were not part of the C standard. Standard-conforming C programs were welcome to define functions with those names, and the rules say that this is perfectly legal and are not references to the identically-named Unix-like functions.
Now, there was a lot of code written for the Microsoft C toolchain that used these sort-of-Unix-ish functions, and renaming those functions would cause those programs to break.
So should we rename the Unix-ish functions in the Microsoft C library, in order to conform to the C standard? Or should we leave the functions in the Microsoft C library under their pre-standard names, to keep existing code working?
The Microsoft C library renamed these Unix-ish function to have a leading underscore. So unlink
became _unlink
, and so on. A program that didn’t use the Unix-ish library functions could define its own function called unlink
, and everything would work just fine. But if the program actually wanted to use the unlink
function from the Unix-ish library, this magic library OLDNAMES.LIB
would step in.
The OLDNAMES.LIB
library doesn’t contain any code of its own. Rather, it contains name redirections that say, “Hey, I have a symbol called unlink
, in case you were looking for it. Wait, you want to know what this symbol represents? Um, it represents a symbol named _unlink
. Good luck with that.”
If the linker cannot find a symbol named unlink
, it turns to OLDNAMES.LIB
as a library of last resort, and that library resolves the symbol unlink
, but replaces it with an unresolved symbol named _unlink
. The linker then goes through the symbol resolution process again, and this time it finds _unlink
in the regular C library.
The net result is that your attempt to call the function unlink
got redirected to the function _unlink
, but only if you didn’t already have a function named unlink
.
You can
suppress the OLDNAMES.LIB
library
in various ways, most notably by passing the /NODEFAULTLIB
flag, which can be abbreviated to the somewhat enigmatic /NOD
.
以上就是本文的全部内容,希望对大家的学习有所帮助,也希望大家多多支持 码农网
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
深入浅出Struts 2
Budi Kuniawan / 杨涛、王建桥、杨晓云 / 人民邮电出版社 / 2009-04 / 59.00元
本书是广受赞誉的Struts 2优秀教程,它全面而深入地阐述了Struts 2的各个特性,并指导开发人员如何根据遇到的问题对症下药,选择使用最合适的特性。作者处处从实战出发,在丰富的示例中直观地探讨了许多实用的技术,如数据类型转换、文件上传和下载、提高Struts 2应用的安全性、调试与性能分析、FreeMarker、Velocity、Ajax,等等。跟随作者一道深入Struts 2,聆听大量来之......一起来看看 《深入浅出Struts 2》 这本书的介绍吧!