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

            <2025年7月>
            293012345
            6789101112
            13141516171819
            20212223242526
            272829303112
            3456789

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            亚洲精品国产美女久久久| 久久99国产精品尤物| 久久久久亚洲AV无码专区网站| 久久亚洲精品国产亚洲老地址| 国产精品成人久久久久三级午夜电影 | 一级a性色生活片久久无少妇一级婬片免费放 | 狠狠狠色丁香婷婷综合久久五月| 无码AV中文字幕久久专区| 久久精品国产2020| 国产精品久久精品| 欧美久久一区二区三区| 精品久久久久久久无码| 久久久精品久久久久特色影视| 97久久久久人妻精品专区 | 国产精品久久新婚兰兰| 久久久久久久久久久久中文字幕| 91久久精品电影| 久久精品aⅴ无码中文字字幕不卡| 久久精品国产免费| 亚洲AV伊人久久青青草原| 91精品国产9l久久久久| 久久久久久国产精品美女| 久久国产美女免费观看精品| 色欲久久久天天天综合网精品| 欧美激情精品久久久久久| 久久久久国产精品| 久久国产亚洲高清观看| 久久成人小视频| 午夜精品久久久久久影视777| 99久久国产热无码精品免费久久久久| 中文字幕精品久久久久人妻| 日韩精品国产自在久久现线拍| 日产精品久久久一区二区| 久久天天婷婷五月俺也去| 国内精品久久久久久久涩爱 | 一级做a爰片久久毛片毛片| 91精品国产综合久久精品| 久久精品亚洲一区二区三区浴池 | www.久久热.com| 日韩人妻无码精品久久免费一 | 欧美成人免费观看久久|