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

            <2025年5月>
            27282930123
            45678910
            11121314151617
            18192021222324
            25262728293031
            1234567

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            久久综合精品国产一区二区三区| 亚洲综合熟女久久久30p| 亚洲国产成人久久精品影视| 国内精品久久久久久久亚洲| 久久久久久久国产免费看| 亚洲欧美国产精品专区久久| 亚洲va久久久噜噜噜久久男同 | 亚洲精品99久久久久中文字幕 | 久久精品国产WWW456C0M| 一本一本久久a久久综合精品蜜桃| 国产午夜免费高清久久影院| 婷婷久久综合九色综合九七| 日本精品久久久久中文字幕| 伊人伊成久久人综合网777| 97久久天天综合色天天综合色hd| 亚洲人成网站999久久久综合 | 亚洲成色999久久网站| 中文精品久久久久人妻不卡| 精品久久久久久国产牛牛app | 久久久久亚洲AV成人片| 人妻少妇精品久久| 国产精品免费久久久久久久久 | 久久久久夜夜夜精品国产| 久久久国产精华液| 综合久久一区二区三区 | 久久综合丁香激情久久| 无码精品久久久久久人妻中字| 一本综合久久国产二区| 久久人人爽人人爽AV片| 久久99久久99小草精品免视看| 国产V综合V亚洲欧美久久| 伊人久久大香线蕉亚洲五月天| 2020国产成人久久精品| 理论片午午伦夜理片久久 | 久久久久婷婷| 久久乐国产精品亚洲综合| 成人精品一区二区久久久| 青青草原综合久久大伊人精品| 99国内精品久久久久久久| 国产高潮国产高潮久久久91| 久久夜色撩人精品国产|