• <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年6月>
            25262728293031
            1234567
            891011121314
            15161718192021
            22232425262728
            293012345

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            国产福利电影一区二区三区久久久久成人精品综合 | 久久精品免费一区二区三区| 日韩人妻无码精品久久久不卡| 中文国产成人精品久久不卡| 久久精品人人做人人妻人人玩| 久久99国产精品久久| 亚洲国产成人久久综合野外| 狠狠色综合网站久久久久久久高清| 996久久国产精品线观看| 久久久久无码中| 久久人爽人人爽人人片AV| 欧美亚洲另类久久综合| 99精品久久精品一区二区| 日韩欧美亚洲综合久久影院d3| 亚洲一级Av无码毛片久久精品| 国产精品99久久99久久久| 人妻无码久久精品| 国产69精品久久久久9999| 亚洲精品无码专区久久久 | 99久久免费国产精品特黄| 午夜欧美精品久久久久久久| 大伊人青草狠狠久久| 久久天天躁狠狠躁夜夜网站 | 国产综合久久久久| 国产成人无码精品久久久性色| 伊人丁香狠狠色综合久久| 久久久精品国产sm调教网站| 精品国产乱码久久久久软件| 欧美性大战久久久久久| 国产成人精品久久一区二区三区av| 久久久久人妻一区二区三区vr| 一级a性色生活片久久无少妇一级婬片免费放| 亚洲午夜久久久久久久久久| 久久人人爽人人爽人人爽| 亚洲精品tv久久久久| 蜜臀久久99精品久久久久久| 久久se这里只有精品| 久久亚洲天堂| 久久久久久伊人高潮影院| 久久天天躁夜夜躁狠狠| 国产毛片欧美毛片久久久|