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

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            日韩精品国产自在久久现线拍| 久久久国产精品福利免费 | AV无码久久久久不卡蜜桃| 青草国产精品久久久久久| 九九热久久免费视频| 久久精品无码一区二区WWW| 99999久久久久久亚洲| 香蕉久久影院| 国产亚州精品女人久久久久久| 国内精品久久久久久久久电影网 | 香蕉久久一区二区不卡无毒影院| 久久精品中文字幕第23页| 久久精品国产亚洲av水果派| 欧美麻豆久久久久久中文| 亚洲国产精品久久久久婷婷软件| 久久精品国产久精国产一老狼| 久久国产V一级毛多内射| 国产精品久久久久jk制服| 国产精品久久久久a影院| 精品久久久久久国产三级| 91久久香蕉国产熟女线看| 91久久精一区二区三区大全| 亚洲va久久久噜噜噜久久狠狠| 无码任你躁久久久久久老妇| 久久精品无码av| 日本加勒比久久精品| 久久婷婷人人澡人人| 欧美一级久久久久久久大片| 精品久久国产一区二区三区香蕉| 青青热久久综合网伊人| 一级做a爰片久久毛片16| 中文字幕亚洲综合久久| AAA级久久久精品无码区| 国产激情久久久久影院| 久久e热在这里只有国产中文精品99 | 国产一区二区三精品久久久无广告 | 狠狠精品久久久无码中文字幕 | 很黄很污的网站久久mimi色| 久久综合久久综合久久综合| 久久se精品一区精品二区| 狠狠干狠狠久久|