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

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            久久精品中文字幕有码| 国产精品一区二区久久精品| 99久久超碰中文字幕伊人| 亚洲综合久久夜AV | 久久综合久久综合亚洲| 久久www免费人成精品香蕉| 91精品国产91久久| 国产精品免费久久久久电影网| 久久中文娱乐网| 久久99精品国产麻豆蜜芽| 91秦先生久久久久久久| 国产精品综合久久第一页| 国产成人综合久久综合| 久久精品国产99国产精偷| 久久最近最新中文字幕大全 | 久久久久久精品无码人妻| 国产一区二区久久久| 色老头网站久久网| 亚洲中文字幕无码久久综合网| 亚洲精品tv久久久久久久久 | 久久精品人成免费| 99久久精品无码一区二区毛片 | 中文字幕一区二区三区久久网站| 精品国产福利久久久| 国产精品午夜久久| 久久人妻AV中文字幕| av无码久久久久久不卡网站| 亚洲国产精品久久久久网站| 久久国产精品二国产精品| 久久久久久久久久久久久久 | 无码伊人66久久大杳蕉网站谷歌| 狠狠色婷婷综合天天久久丁香| 久久久久这里只有精品 | 亚洲精品美女久久久久99| 精品久久久久久久| 久久综合亚洲色HEZYO国产| 午夜不卡久久精品无码免费| 狠狠久久综合伊人不卡| 久久久久无码精品国产不卡| 久久久久亚洲精品男人的天堂| 无码人妻精品一区二区三区久久 |