• <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 閱讀(1895) 評論(0)  編輯 收藏 引用 所屬分類: C++

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

            導航

            統計

            常用鏈接

            留言簿(1)

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            国产亚洲美女精品久久久| 久久人人爽人人爽人人片AV麻烦| 欧美精品乱码99久久蜜桃| 2020国产成人久久精品| 亚洲综合日韩久久成人AV| 国产亚洲精品美女久久久| 国产精品18久久久久久vr| 三级韩国一区久久二区综合| 久久亚洲AV成人无码电影| 品成人欧美大片久久国产欧美| 99久久免费国产精品特黄| 久久久久久人妻无码| 美女久久久久久| 91精品国产91久久综合| 欧美国产成人久久精品| 97精品国产91久久久久久| 少妇人妻综合久久中文字幕| 久久99国产精品久久99| 久久精品国产色蜜蜜麻豆| 国产精品热久久无码av| 精品久久久久香蕉网| 热久久最新网站获取| 精品久久久久中文字幕一区| 久久青青草原亚洲av无码app| 日韩AV毛片精品久久久| 久久综合久久综合久久综合| 一本久久知道综合久久| 婷婷久久综合| 国内精品久久久久影院网站 | 午夜视频久久久久一区 | 亚洲中文字幕无码久久2017| 国产精品激情综合久久| 久久国产色av免费看| 日本亚洲色大成网站WWW久久| 精品视频久久久久| 亚洲欧美日韩精品久久| 久久精品国产半推半就| 丰满少妇人妻久久久久久| 久久久久亚洲AV无码专区体验| 日本久久久久亚洲中字幕| 无码AV波多野结衣久久|