• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            <2009年2月>
            25262728293031
            1234567
            891011121314
            15161718192021
            22232425262728
            1234567

            統計

            • 隨筆 - 24
            • 文章 - 0
            • 評論 - 17
            • 引用 - 0

            常用鏈接

            留言簿(4)

            隨筆分類

            隨筆檔案

            相冊

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            有關include guard的一個好帖子(收藏)
            終于弄清楚了原來說的同一個頭文件不能被兩次或兩次以上包含是針對同一個源文件而言的。借用80后的流行語,真是漢哪!

            原貼地址:http://www.keil.com/forum/docs/thread10237.asp

            作者 Per Westermark

            The

            #ifndef xx
            #define xx
            ...
            #endif
            

            method is to make sure that a header file isn't included more than once from the same c file.

            You can not - and normally don't want to - stop multiple c files from including the same header file.

            A header file is included because:
            1) You have specifically added a line #include "xx" or #include <xx> in the source file. Don't do that unless you want the file to be included :)
            2) You are including one header file, that it it's turn (one or more steps away) includes another header file. But a header file should only contain a recursive #include if it really needs that other file for some declarations. Hence, you need to include it.

            What does this mean?

            If the header file must be seen by multiple source files, you can't use it to allocate global variables, since the linker would then complain about multiple sets of global variables with the same name. This can be solved with the following:

            //globals.h
            #ifndef _GLOBALS_H
            #define _GLOBALS_H
            #if defined MAIN
            #define EXTERN
            #else
            #define EXTERN extern
            #endif
            ...
            EXTERN int my_global_variable;
            #endif // _GLOBALS_H
            

            // main.c
            #define MAIN
            #include "globals.h"
            ...
            // misc.c
            #include "globals.h"
            ...
            

            In this case, only the inclusion in main.c will result in an "allocation" of global variables, because the #define EXTERN will be empty. All other source files that includes "globals.h" will just see the type information for the global variables.

            posted on 2009-02-19 09:04 小蔥蘸醬 閱讀(999) 評論(2)  編輯 收藏 引用

            評論

            # re: 有關include guard的一個好帖子(收藏) 2009-02-19 21:19 陳梓瀚(vczh)

            EXTERN的時候,如果剛好main沒有引用它,那就鏈接錯誤了- -#
              回復  更多評論    

            # re: 有關include guard的一個好帖子(收藏)[未登錄] 2009-02-20 16:15 小蔥蘸醬

            @陳梓瀚(vczh)
            歡迎評論!
            只要在include "globals.h"前定義了MAIN,就不會聯接錯誤,跟引用有什么關系呢?
              回復  更多評論    
            久久人人爽人人爽人人爽| 亚洲AV无码久久精品蜜桃| 精品久久久久久中文字幕| 久久福利青草精品资源站| 国产精品美女久久久| 777久久精品一区二区三区无码| 中文精品久久久久国产网址| 久久久久99精品成人片| 亚洲乱码精品久久久久..| 人人狠狠综合久久亚洲婷婷| 97视频久久久| 日本免费久久久久久久网站| 久久免费大片| 狠狠狠色丁香婷婷综合久久五月| 久久国产香蕉视频| A狠狠久久蜜臀婷色中文网| 久久精品无码一区二区app| 久久国产精品成人影院| 久久久久久久91精品免费观看 | 久久99精品久久久久久秒播| 久久精品国产色蜜蜜麻豆| 国产精品一区二区久久精品无码| 亚洲熟妇无码另类久久久| 日韩精品国产自在久久现线拍| 久久久久久久精品成人热色戒| 91精品国产91久久久久久蜜臀| 久久久久久精品免费看SSS| 久久99精品久久久久久齐齐| 国产一级持黄大片99久久| 一本色道久久88—综合亚洲精品 | 亚洲国产精品成人久久| 亚洲&#228;v永久无码精品天堂久久| 热re99久久精品国99热| 免费精品久久久久久中文字幕| 色综合久久88色综合天天| 久久99精品久久久久久久不卡| 久久亚洲国产精品成人AV秋霞| 亚洲人成无码www久久久| 国产叼嘿久久精品久久| 国产激情久久久久影院| 国产成人久久精品二区三区|