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

            huangyi5209

              C++博客 :: 首頁 :: 聯(lián)系 :: 聚合  :: 管理
              0 Posts :: 13 Stories :: 0 Comments :: 0 Trackbacks

            常用鏈接

            留言簿

            我參與的團(tuán)隊

            搜索

            •  

            最新評論

            Pointers and references look different enough (pointers use the “*” and “->” operators, references use “.“), but they seem to do similar things. Both pointers and references let you refer to other objects indirectly. How, then, do you decide when to use one and not the other?

            First, recognize that there is no such thing as a null reference. A reference must always refer to some object. As a result, if you have a variable whose purpose is to refer to another object, but it is possible that there might not be an object to refer to, you should make the variable a pointer, because then you can set it to null. On the other hand, if the variable must alwaysrefer to an object, i.e., if your design does not allow for the possibility that the variable is null, you should probably make the variable a reference.

            “But wait,” you wonder, “what about underhandedness like this?”

            1. char *pc = 0;          // set pointer to null   
            2. char& rc = *pc;        // make reference refer to   
            3.                        // dereferenced null pointer  

            Well, this is evil, pure and simple. The results are undefined (compilers can generate output to do anything they like), and people who write this kind of code should be shunned until they agree to cease and desist. If you have to worry about things like this in your software, you’re probably best off avoiding references entirely. Either that or finding a better class of programmers to work with. We’ll henceforth ignore the possibility that a reference can be “null.”

            Because a reference must refer to an object, C++ requires that references be initialized:

            string& rs;             // error! References must   
            1.                         // be initialized   
            2. string s("xyzzy");   
            3. string& rs = s;         // okay, rs refers to s  

            Pointers are subject to no such restriction:

            1. string *ps;             // uninitialized pointer:   
            2.                         // valid but risky  

            The fact that there is no such thing as a null reference implies that it can be more efficient to use references than to use pointers. That’s because there’s no need to test the validity of a reference before using it:

            void printDouble(const double& rd)   
            1. {   
            2.     cout << rd;         // no need to test rd; it   
            3. }                       // must refer to a double  

            Pointers, on the other hand, should generally be tested against null:

            1. void printDouble(const double *pd)   
            2. {   
            3. if (pd) {             // check for null pointer   
            4. cout << *pd;   
            5. }   
            6. }  

            Another important difference between pointers and references is that pointers may be reassigned to refer to different objects. A reference, however, always refers to the object with which it is initialized:

            1. string s1("Nancy");   
            2. string s2("Clancy");   
            3. string& rs = s1;         // rs refers to s1   
            4.   
            5. string *ps = &s1;        // ps points to s1<A name=31186></A>   
            6.   
            7. rs = s2;                 // rs still refers to s1,   
            8.                          // but s1's value is now   
            9.                          // "Clancy"   
            10.   
            11. ps = &s2;                // ps now points to s2;   
            12.                          // s1 is unchanged  

            In general, you should use a pointer whenever you need to take into account the possibility that there’s nothing to refer to (in which case you can set the pointer to null) or whenever you need to be able to refer to different things at different times (in which case you can change where the pointer points). You should use a reference whenever you know there will always be an object to refer to and you also know that once you’re referring to that object, you’ll never want to refer to anything else.

            References, then, are the feature of choice when you know you have something to refer to, when you’ll never want to refer to anything else, and when implementing operators whose syntactic requirements make the use of pointers undesirable. In all other cases, stick with pointers.

            posted on 2011-01-24 20:29 huangyi5209 閱讀(267) 評論(0)  編輯 收藏 引用 所屬分類: C/C++
            97精品依人久久久大香线蕉97| 久久精品中文闷骚内射| 青青草国产成人久久91网| 久久久久久久波多野结衣高潮| 精品伊人久久大线蕉色首页| 无码久久精品国产亚洲Av影片 | 无码任你躁久久久久久老妇App| 99久久成人18免费网站| 性做久久久久久久久老女人 | 久久九九有精品国产23百花影院| 狠色狠色狠狠色综合久久 | 亚洲国产成人久久精品动漫| 久久精品无码免费不卡| 漂亮人妻被黑人久久精品| 国产A级毛片久久久精品毛片| 模特私拍国产精品久久| 久久夜色精品国产亚洲| 久久人人爽人人爽人人片AV东京热 | 久久婷婷久久一区二区三区| 亚洲色欲久久久久综合网| 国产一区二区精品久久| 久久久这里有精品| 精品多毛少妇人妻AV免费久久| 久久久久亚洲AV无码网站| 一级a性色生活片久久无| 久久免费线看线看| 久久精品国产亚洲AV香蕉| 中文字幕亚洲综合久久菠萝蜜 | 精品伊人久久久| 久久精品成人一区二区三区| MM131亚洲国产美女久久| 亚洲国产另类久久久精品小说 | 免费观看久久精彩视频| 久久久久亚洲精品天堂| 亚洲精品无码久久久久| 亚洲中文久久精品无码| 久久久久久久波多野结衣高潮 | 久久久久久无码国产精品中文字幕| 精品久久久久久久| 久久精品草草草| 91久久九九无码成人网站 |