• <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 閱讀(1895) 評論(0)  編輯 收藏 引用 所屬分類: C++

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

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            欧美精品福利视频一区二区三区久久久精品 | 久久综合九色综合欧美狠狠| 久久久久无码精品国产| 99久久99久久久精品齐齐| 国产三级观看久久| 青青草原综合久久大伊人| 亚洲精品国产美女久久久| 国产叼嘿久久精品久久| 午夜久久久久久禁播电影| 国产成人精品久久一区二区三区av | 国产精品99久久久精品无码| 精品免费久久久久久久| 久久久精品国产亚洲成人满18免费网站| 久久久久久极精品久久久| 精品少妇人妻av无码久久| 久久国产精品波多野结衣AV| 精品国产乱码久久久久久呢| 亚洲国产精品久久久久久| 囯产极品美女高潮无套久久久 | 偷偷做久久久久网站| 色综合色天天久久婷婷基地| 亚洲精品乱码久久久久66| 久久香蕉国产线看观看猫咪?v| 国内精品伊人久久久久av一坑| 99久久这里只精品国产免费| 国产综合精品久久亚洲| MM131亚洲国产美女久久| 欧美黑人又粗又大久久久| 久久精品国产2020| 亚洲国产成人久久综合碰| 狠狠色丁香婷婷综合久久来来去| 久久精品aⅴ无码中文字字幕重口| 久久久久亚洲av综合波多野结衣| 精品久久久久久久久免费影院 | 中文字幕一区二区三区久久网站| 久久狠狠高潮亚洲精品| 亚洲综合伊人久久综合| 亚洲狠狠婷婷综合久久久久| 久久精品a亚洲国产v高清不卡| 久久精品aⅴ无码中文字字幕不卡| 久久精品欧美日韩精品|