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

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            亚洲欧美日韩久久精品第一区| 国产国产成人精品久久| 国产亚州精品女人久久久久久 | 狠狠精品干练久久久无码中文字幕 | 色综合合久久天天给综看| 97久久国产露脸精品国产| 9999国产精品欧美久久久久久 | 97超级碰碰碰碰久久久久| 国内精品久久久久影院薰衣草 | 97久久精品午夜一区二区| 亚洲&#228;v永久无码精品天堂久久| 久久成人国产精品免费软件| 精品无码久久久久久国产| 热re99久久精品国99热| 亚洲国产精品无码久久九九| 99久久婷婷国产综合精品草原| MM131亚洲国产美女久久| 久久久艹| 91久久精品视频| 99re这里只有精品热久久| 久久福利资源国产精品999| 精品久久久无码中文字幕| 2021久久精品国产99国产精品| 久久www免费人成看片| 香蕉久久永久视频| 久久久精品视频免费观看| 狠狠色丁香婷婷综合久久来| 国内精品久久久久久久97牛牛| 精品国产99久久久久久麻豆| 亚洲&#228;v永久无码精品天堂久久 | 久久99精品九九九久久婷婷| 国产三级观看久久| 久久精品国产国产精品四凭| 国产精品99久久精品爆乳| 999久久久国产精品| 久久精品中文字幕第23页| 久久久国产精品| 国产精品久久久久久久人人看| 亚洲伊人久久成综合人影院| 国内精品综合久久久40p| 亚洲午夜久久久久妓女影院|