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

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


            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()函數(shù)引用的是全局?jǐn)?shù)據(jù). 所以早期的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.(數(shù)據(jù)成員定義還是要放在最前面)

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

            只有注冊用戶登錄后才能發(fā)表評論。
            網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問   Chat2DB   管理



            <2006年4月>
            2627282930311
            2345678
            9101112131415
            16171819202122
            23242526272829
            30123456

            常用鏈接

            留言簿(7)

            隨筆檔案

            最新隨筆

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            99久久无码一区人妻| 色综合久久中文字幕无码 | 久久精品无码专区免费| 狠狠人妻久久久久久综合| 性做久久久久久久久久久| 国产亚洲精品久久久久秋霞| 久久久久亚洲AV成人片| 久久精品国产精品亚洲人人| 国产精品中文久久久久久久| 久久99精品综合国产首页| 久久久久亚洲爆乳少妇无| 人妻精品久久久久中文字幕69 | 人妻无码αv中文字幕久久| 久久久久久免费一区二区三区 | 久久久久一级精品亚洲国产成人综合AV区| 麻豆国内精品久久久久久| 久久精品夜夜夜夜夜久久| 久久婷婷五月综合成人D啪| 精品久久无码中文字幕| 久久久一本精品99久久精品88| .精品久久久麻豆国产精品| 思思久久99热免费精品6| 91久久精品电影| 国产精品99久久免费观看| 精品伊人久久久| 亚洲精品无码久久久| 免费精品久久久久久中文字幕| 久久亚洲精品中文字幕三区| 久久99热只有频精品8| 亚洲精品乱码久久久久久蜜桃图片 | 94久久国产乱子伦精品免费| 色欲久久久天天天综合网精品| 欧美久久亚洲精品| 久久夜色撩人精品国产| 国产精品VIDEOSSEX久久发布| 97久久精品午夜一区二区| 日韩人妻无码精品久久免费一| 一本色道久久99一综合| 人妻无码αv中文字幕久久琪琪布 人妻无码久久一区二区三区免费 人妻无码中文久久久久专区 | 国产精自产拍久久久久久蜜| 中文字幕亚洲综合久久2|