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

            隨筆分類

            隨筆檔案

            搜索

            最新評論

            閱讀排行榜

            評論排行榜

            久久久久亚洲av无码专区导航| 国产精品一区二区久久| 亚洲欧洲精品成人久久奇米网| 欧美精品九九99久久在观看| 国产亚洲精品久久久久秋霞| 久久99免费视频| 亚洲精品无码久久毛片| 97久久精品无码一区二区天美| 青春久久| 伊人久久精品线影院| 久久天天躁狠狠躁夜夜avapp| 国产精品欧美久久久久无广告| 久久精品日日躁夜夜躁欧美| 久久99精品久久久久久水蜜桃| 久久久久亚洲AV无码观看| 国产日韩久久免费影院| 久久久精品国产sm调教网站 | 丁香五月网久久综合| 亚洲精品国产自在久久| 久久精品嫩草影院| 久久夜色精品国产欧美乱| 久久精品综合网| 无码任你躁久久久久久| 久久精品三级视频| 99久久国产热无码精品免费久久久久 | 国产精品伦理久久久久久| 国产精品99久久99久久久| 99久久国产精品免费一区二区| 伊人精品久久久久7777| 亚洲欧洲中文日韩久久AV乱码| 国内精品伊人久久久久影院对白| 精品久久久久久久久午夜福利| 久久精品中文字幕大胸| 国产69精品久久久久9999APGF| 久久中文字幕视频、最近更新| 国内精品久久久久久久久电影网| 伊人色综合久久天天| 狠狠综合久久综合中文88| 亚洲第一永久AV网站久久精品男人的天堂AV| 国产精品福利一区二区久久| 色综合久久天天综合|