• <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>

            C++ library系列 -- STL實現中的ODR “one-definition-rule” for types

            Linking issue
            - While different modules (.obj) using istreambuf_iterator/ostreambuf_iterator, compiled with different options on HID/no-HID and SCL/no-SCL, these modules could not be linked successfully;

            The error comes directly from the CLR when a type has multiple definitions that are not consistent based upon the ODR, one-definition-rule for types. And, the linker itself isn't involved.

            For example, with one module compile with /D_SECURE_SCL=0, while another is compiled with _SECURE_SCL=1;

            At first, it's found that with _SECURE_SCL, the only thing that could be different as following,

            #if _SECURE_SCL
                typedef _Range_checked_iterator_tag _Checked_iterator_category;
            #endif

            But, actually, it's not the typedef that changed the layout the these iterators (istreambuf_iterator/ostreambuf_iterator), and further they don't really use the extra pointer that _SECURE_SCL adds.

            Finally, it's found the root cause is that, these iterators, istreambuf_iterator/ostreambuf_iterator  had been moved from <xutility> to <streambuf>, and their ultimate base class had been changed from _Iterator_base_secure to _Iterator_base. And, the layout of _Iterator_base would be different between HID and no-HID, and between SCL and no-SCL. It is the cause where the issue comes from.

            What we can learn from such issue,
            These iterators really shouldn't derive from either _Iterator_base_secure or _Iterator_base, because these classes contain data members (pointers) which are entirely unused. It would result in unnecessary bloat and extra work being performed in ctor/dtor etc.

            Introduce a new class, _Iterator_base_universal, which is defined identically regardless of HID/no-HID and SCL/no-SCL. It would contains the three internal typedefs that all standard iterators need to have, and nothing else. And _Iterator_base (in all of its variants) and _Iterator_base_secure now should derive from _Iterator_base_universal to get these typedefs.

            Now, when an iterator wants these typedefs, but not the data members of _Iterator_base and _Iterator_base_secure, it could derive from _Iterator_base_universal. And istreambuf_iterator and ostreambuf_iterator are now as small as possible, and keep identical representations or layout across HID/no-HID, SCL/no-SCL.

            posted on 2010-12-19 11:09 flagman 閱讀(1900) 評論(0)  編輯 收藏 引用 所屬分類: C++

            <2010年12月>
            2829301234
            567891011
            12131415161718
            19202122232425
            2627282930311
            2345678

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            97久久国产露脸精品国产| 久久久国产一区二区三区| 一本久久知道综合久久| 97热久久免费频精品99| 国产精品嫩草影院久久| 久久中文字幕人妻熟av女| AV无码久久久久不卡网站下载| 久久精品国产精品亚洲艾草网美妙| 久久99热这里只频精品6| 亚洲国产成人久久综合一| 国产精品99久久久久久宅男小说| 久久99精品综合国产首页| 人人狠狠综合88综合久久| 97久久久久人妻精品专区 | 亚洲一本综合久久| 久久久亚洲裙底偷窥综合| 婷婷综合久久狠狠色99h| 久久狠狠爱亚洲综合影院| 97久久精品无码一区二区天美 | 欧美伊人久久大香线蕉综合69 | 人妻精品久久久久中文字幕一冢本| 欧美一区二区精品久久| 久久99精品久久久久久动态图| 午夜精品久久影院蜜桃| 久久精品免费网站网| 国产精品久久久久乳精品爆| AV无码久久久久不卡网站下载| 亚洲AV日韩精品久久久久久久| 亚洲国产成人精品女人久久久 | 久久久国产精品福利免费| 无码AV中文字幕久久专区| 亚洲欧美日韩精品久久亚洲区| 国产伊人久久| 久久精品国内一区二区三区 | 久久无码精品一区二区三区| 欧美亚洲另类久久综合| 国产激情久久久久影院老熟女免费 | 国产午夜电影久久| 久久国产午夜精品一区二区三区| 国产精品激情综合久久| 久久久人妻精品无码一区 |