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

            <2010年12月>
            2829301234
            567891011
            12131415161718
            19202122232425
            2627282930311
            2345678

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            久久99精品国产麻豆宅宅| 久久久亚洲AV波多野结衣| 久久久综合九色合综国产| 99久久免费国产精精品| 久久精品9988| 久久精品国产亚洲AV久| 五月丁香综合激情六月久久| 久久精品国产第一区二区三区| 久久er国产精品免费观看2| 欧美一级久久久久久久大| 国产麻豆精品久久一二三| 久久午夜综合久久| 久久久久亚洲av无码专区| 久久久久18| 97久久精品国产精品青草| 亚洲国产成人精品久久久国产成人一区二区三区综 | 亚洲第一极品精品无码久久| 久久人人添人人爽添人人片牛牛| 久久国产乱子精品免费女| 久久亚洲国产成人影院| 亚洲一本综合久久| 久久午夜伦鲁片免费无码| 久久天天躁狠狠躁夜夜avapp| 91亚洲国产成人久久精品| 日本久久久久亚洲中字幕| 无码人妻久久一区二区三区蜜桃| 7国产欧美日韩综合天堂中文久久久久| 国产A级毛片久久久精品毛片| 久久国产免费直播| 久久se精品一区二区| 精品久久久无码人妻中文字幕豆芽 | 岛国搬运www久久| 久久无码专区国产精品发布 | 国产香蕉久久精品综合网| 国产精品熟女福利久久AV| 久久九九亚洲精品| 国产精品久久久久久福利69堂| 久久久精品人妻一区二区三区蜜桃 | 久久天天躁狠狠躁夜夜不卡| 国产精品99久久久久久董美香 | 欧美激情一区二区久久久|