• <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>
            asm, c, c++ are my all
            -- Core In Computer
            posts - 139,  comments - 123,  trackbacks - 0

            /********************************************\
            |????歡迎轉載, 但請保留作者姓名和原文鏈接, 祝您進步并共勉!???? |
            \********************************************/


            C++對象模型(9) - 3.1 The Binding of a Data Member

            作者: Jerry Cat
            時間: 2006/11/15
            鏈接:?
            http://m.shnenglu.com/jerysun0818/archive/2006/11/15/15186.html


            3.1 The Binding of a Data Member

            Consider the following program fragment:.

            // A third party foo.h header file
            // pulled in from somewhere
            extern float x;

            // the programmer's Point3d.h file
            class Point3d
            {
            public:
            ?? Point3d( float, float, float );
            ?? // question:? which x is returned and set?
            ?? float X() const { return x; }
            ?? void X( float new_x ) const { x = new_x; }
            ?? // ...
            private:
            ?? float x, y, z;
            };
            If I were to ask which x the Point3d member X() returns—the class instance or the extern instance—everyone today would answer the class instance, and everyone would be right. Most everyone, however, would probably be surprised to learn that this answer was not always correct.

            早期的C++將其解析為X()函數引用的是全局數據. 所以早期的C++程序員發(fā)明了倆防范寫法(至今還有人用):
            (1). Placing all data members first in the class declaration to ensure the right binding:

            class Point3d
            {
            ?? // defensive programming style #1
            ?? // place all data first ...
            ?? float x, y, z;
            public:
            ?? float X() const { return x; }
            ?? // ... etc. ...
            };

            (2). Placing all inline functions, regardless of their size, outside the class declaration:

            class Point3d
            {
            public:
            ?? // defensive programming style #2
            ?? // place all inlines outside the class
            ?? Point3d();
            ?? float X() const;
            ?? void X( float ) const;
            ?? // ... etc. ...
            };
            inline float
            Point3d::
            X() const
            {
            ?? return x;
            }

            // ... etc. ...


            extern int x;

            class Point3d
            {
            public:
            ?? ...
            ?? // analysis of function body delayed until
            ?? // closing brace of class declaration seen.
            ?? float X() const { return x; }
            ?? ...
            private:
            ?? float x;
            ?? ...
            };

            // in effect, analysis is done here
            the analysis of the member function's body is delayed until the entire class declaration is seen. Thus the binding of a data member within the body of an inline member function does not occur until after the entire class declaration is seen.

            但是This is not true of the argument list of the member function, however. Names within the argument list are still resolved in place at the point they are first encountered. Nonintuitive bindings between extern and nested type names, therefore, can still occur. In the following code fragment, for example, the type of length in both member function signatures resolves to that of the global typedef—that is, to int. When the subsequent declaration of the nested typedef of length is encountered, the Standard requires that the earlier bindings be flagged as illegal:

            typedef int length;

            class Point3d
            {
            public:
            ?? // oops: length resolves to global
            ?? // ok: _val resolves to Point3d::_val
            ?? mumble( length val ) { _val = val; }
            ?? length mumble() { return _val; }
            ?? // ...

            private:
            ?? // length must be seen before its first
            ?? // reference within the class.? This
            ?? // declaration makes the prior reference illegal.
            ?? typedef float length;
            ?? length _val;
            ?? // ...
            };
            This aspect of the language still requires the general defensive programming style of always placing nested type declarations at the beginning of the class. In our example, placing the nested typedef defining length above any of its uses within the class corrects the nonintuitive binding.(數據成員定義還是要放在最前面)

            posted on 2006-11-15 17:04 Jerry Cat 閱讀(499) 評論(0)  編輯 收藏 引用

            <2006年11月>
            2930311234
            567891011
            12131415161718
            19202122232425
            262728293012
            3456789

            常用鏈接

            留言簿(7)

            隨筆檔案

            最新隨筆

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            国产高潮国产高潮久久久91 | 99久久国产综合精品五月天喷水| 久久发布国产伦子伦精品| 99久久无码一区人妻a黑| 久久久久久毛片免费看| 久久久久无码精品国产不卡| 久久国产成人亚洲精品影院| 亚洲va中文字幕无码久久 | 久久这里只有精品首页| 久久久久久久99精品免费观看| 欧美粉嫩小泬久久久久久久 | 韩国三级中文字幕hd久久精品| 色综合久久久久无码专区| 久久久青草青青国产亚洲免观| 精品久久久久久成人AV| 久久人人爽人人爽人人爽| 久久一区二区三区免费| 日本免费久久久久久久网站| 亚洲va久久久噜噜噜久久狠狠| 四虎国产精品成人免费久久| 精品免费久久久久国产一区| 久久无码av三级| 青青热久久综合网伊人| 99久久成人国产精品免费| 人妻无码αv中文字幕久久| 三级三级久久三级久久| 久久青青色综合| 久久天天躁夜夜躁狠狠躁2022| 久久亚洲国产成人影院| 亚洲午夜精品久久久久久浪潮 | 精品久久久久久无码不卡| 久久精品18| 麻豆久久| 午夜天堂av天堂久久久| 中文字幕乱码人妻无码久久| 亚洲国产美女精品久久久久∴| 久久精品国产亚洲AV蜜臀色欲| 伊人色综合久久天天人手人婷 | 无码任你躁久久久久久| 久久福利资源国产精品999| 超级97碰碰碰碰久久久久最新|