如何防止变量重复定义（How to prevent variables from being redefined）.docVIP

下载本文档

12
0
约3.77千字
约 7页
2017-09-07 发布于河南
举报
版权申诉

如何防止变量重复定义（How to prevent variables from being redefined）.doc

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

如何防止变量重复定义（How to prevent variables from being redefined）

如何防止变量重复定义（How to prevent variables from being redefined） The problem of repeating definitions when a custom header file is referenced in multiple files (C language) I wrote a header file, but when I referenced it in multiple.C files, it prompted me to repeat the definition and use conditional compiled statements. The header files are as follows: (mainly defining some global variables) File name: identifier.h Content: #ifndef identifier_h #define identifier_h Int, a, B, c; Float, D, e, f; Int, m[5], n[5]; #endif This is the form of header file, but when I refer to it in the two.C file, I suggest repeating the definition. The.C file follows: File name: sub1.c Content: #include identifier.h Void, sub11 () { If (ab) { M[0]=a+d; } Else { M[0]=b+d; } } File name: sub2.c Content: #include identifier.h Void sub22 (int i) { If (d=m[i]) { A=0; } Else { B=0; } } Answer: you need to add extern keywords to the header file that defines the variables! Then you can use the variables defined in other files (no need to add keywords extern)! #ifndef identifier_h #define identifier_h .... #endif This set of conditions is compiled to prevent multiple.H files from being included in the same.C file (for example, a.C file containing A.H, and A.H containing the B.H), Then, when you include both A.H and B.H in this.C file, there is no error because of the above conditional compilation. Because the compiler is compiling It is compiled in accordance with the.C file, and each.C file is compiled into a.O file (Linux system) or.Obj (Windows system), These.O files are then linked together and finally linked to the runtime to form executable files (ELF or exe files). You include the same.H file in the two.C files. This has nothing to do with conditional compilation. You defined the global variables a, B, C in the.H file. So, in your two.C files, each.C file has such global variable definitions: int, a, B, C; when each.C file is compiled separately, of course, no problem, But when they link up, the