• <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精品国产| 久久se精品一区二区| 亚洲国产精品无码久久久久久曰 | 99国产精品久久久久久久成人热| 91亚洲国产成人久久精品网址| 亚洲国产成人精品91久久久 | 亚洲精品乱码久久久久久中文字幕| 国产精品一久久香蕉国产线看观看| 久久99热这里只有精品国产| 亚洲国产另类久久久精品小说| 中文字幕一区二区三区久久网站| 久久综合亚洲鲁鲁五月天| 国产99久久久国产精品~~牛| 色妞色综合久久夜夜| 国内精品久久久久久久影视麻豆| 影音先锋女人AV鲁色资源网久久| 久久精品无码一区二区日韩AV| 精品久久久久久中文字幕人妻最新| 亚洲国产精品无码久久青草| segui久久国产精品| 久久国产精品久久国产精品| 午夜久久久久久禁播电影| 亚洲精品无码久久久| 久久精品夜色噜噜亚洲A∨| 亚洲国产成人久久精品影视| 69久久精品无码一区二区| 久久丫精品国产亚洲av不卡 | 久久精品欧美日韩精品| 亚洲国产美女精品久久久久∴ | 久久人人爽人人精品视频| 精品久久久久久无码人妻热| 成人久久免费网站| 99久久亚洲综合精品网站| 一级做a爰片久久毛片16| 亚洲国产成人久久综合一区77| 精品久久久久久亚洲| 青青草原1769久久免费播放| 久久九九青青国产精品|