Click here to Skip to main content
15,867,453 members
Articles / Programming Languages / C++

An Insight to References in C++

Rate me:
Please Sign up or sign in to vote.
3.52/5 (46 votes)
18 Apr 2006CPOL4 min read 163K   37   73
How C++ Compiler handles References

Introduction

I choose to write about references in C++ because I feel most of the people have misconceptions about references. I got this feeling because I took many C++ interviews and I seldom get correct answers about references in C++.

What is meant by references in C++? A reference is generally thought of as an aliasing of the variable it refers to. I hate the definition of references being an alias of a variable in C++. In this article, I will try to explain that there is nothing known as aliasing in C++.

Background

Both in C and in C++, there are only two ways by which a variable can be accessed, passed, or retrieved. The two ways are: 

  1. Accessing/passing variable by value
  2. Accessing/Passing variable by address - In this case pointers will come into the picture

There is no 3rd way of accessing/passing variables. A reference variable is just another pointer variable which will take its own space in memory. The most important thing about the references is that it's a type of pointer which gets automatically dereferenced (by compiler). Hard to believe? Let's see....

A Sample C++ Code using References

Lets write a simple C++ code which will use references:

C++
#include <iostream.h>
int main()
{
    int i = 10;   // A simple integer variable
    int &j = i;   // A Reference to the variable i
    
    j++;   // Incrementing j will increment both i and j.

    // check by printing values of i and j
    cout<<  i  <<  j  <<endl; // should print 11 11

    // Now try to print the address of both variables i and j
    cout<<  &i  <<  &j  <<endl; 
    // surprisingly both print the same address and make us feel that they are
    // alias to the same memory location. 
    // In example below we will see what is the reality
    return 0;
}

References are nothing but constant pointers in C++. A statement int &i = j; will be converted by the compiler to int *const i = &j; i.e. References are nothing but constant pointers. They need initialization because constants must be initialized and since the pointer is constant, they can't point to anything else. Let's take the same example of references in C++ and this time we will use the syntax that the compiler uses when it sees references.

A Sample C++ Code using References (Compiler Generated Syntax)

C++
#include <iostream.h>
int main()
{
    int i = 10;   		// A simple integer variable
    int *const j = &i;   	// A Reference to the variable i
    
    (*j)++;   		// Incrementing j. Since reference variables are 
			// automatically dereferenced by compiler

    // check by printing values of i and j
    cout<<  i  <<  *j  <<endl; // should print 11 11
    // A * is appended before j because it used to be reference variable
    // and it should get automatically dereferenced.
    return 0;
}

You must be wondering why I skipped the printing of address from the above example. This needs some explanation. Since reference variables are automatically dereferenced, what will happen to a statement like cout << &j << endl;. The compiler will convert the statement into cout << &*j << endl; because the variable gets automatically dereferenced. Now &* cancels each other. They become meaningless and cout prints the value at j which is nothing but the address of i because of the statement int *const j = &i;.

So the statement cout << &i << &j << endl; becomes cout << &i << &*j << endl; which is similar to printing the address of i in both the cases. This is the reason behind the same address being displayed while we try to print normal variables as well as reference variables.

A Sample C++ Code using Reference Cascading

Here we will try to look at a complex scenario and see how references will work in cascading. Let's follow the code below:

C++
#include <iostream.h>
int main()
{
    int i = 10; // A Simple Integer variable
    int &j = i; // A Reference to the variable
    // Now we can also create a reference to reference variable. 
    int &k = j; // A reference to a reference variable
    // Similarly we can also create another reference to the reference variable k
    int &l = k; // A reference to a reference to a reference variable.

    // Now if we increment any one of them the effect will be visible on all the
    // variables.
    // First print original values
    // The print should be 10,10,10,10
    cout<<  i  <<  ","  <<  j  <<  ","  <<  k  <<  ","  <<  l  <<endl;
    // increment variable j
    j++; 
    // The print should be 11,11,11,11
    cout<<  i  <<  ","  <<  j  <<  ","  <<  k  <<  ","  <<  l  <<endl;
    // increment variable k
    k++;
    // The print should be 12,12,12,12
    cout<<  i  <<  ","  <<  j  <<  ","  <<  k  <<  ","  <<  l  <<endl;
    // increment variable l
    l++;
    // The print should be 13,13,13,13
    cout<<  i  <<  ","  <<  j  <<  ","  <<  k  <<  ","  <<  l  <<endl;
    return 0;
}

A sample C++ Code Using Reference Cascading (Compiler Generated Syntax)

Here we will see if we won't depend upon the compiler to generate constant pointers in place of reference and auto dereferencing the constant pointer, we can achieve the same results.

C++
#include <iostream.h>
int main()
{
    int i = 10;         // A Simple Integer variable
    int *const j = &i;     // A Reference to the variable
    // The variable j will hold the address of i

    // Now we can also create a reference to reference variable. 
    int *const k = &*j;     // A reference to a reference variable
    // The variable k will also hold the address of i because j 
    // is a reference variable and 
    // it gets auto dereferenced. After & and * cancels each other 
    // k will hold the value of
    // j which it nothing but address of i

    // Similarly we can also create another reference to the reference variable k
    int *const l = &*k;     // A reference to a reference to a reference variable.
    // The variable l will also hold address of i because k holds address of i after
    // & and * cancels each other.

    // so we have seen that all the reference variable will actually holds the same
    // variable address.

    // Now if we increment any one of them the effect will be visible on all the
    // variables.
    // First print original values. The reference variables will have * prefixed because 
    // these variables gets automatically dereferenced.

    // The print should be 10,10,10,10
    cout<<  i  <<  ","  <<  *j  <<  ","  <<  *k  <<  ","  <<  *l  <<endl;
    // increment variable j
    (*j)++; 
    // The print should be 11,11,11,11
    cout<<  i  <<  ","  <<  *j  <<  ","  <<  *k  <<  ","  <<  *l  <<endl;
    // increment variable k
    (*k)++;
    // The print should be 12,12,12,12
    cout<<  i  <<  ","  <<  *j  <<  ","  <<  *k  <<  ","  <<  *l  <<endl;
    // increment variable l
    (*l)++;
    // The print should be 13,13,13,13
    cout  <<  i  <<  ","  <<  *j  <<  ","  <<  *k  <<  ","  <<  *l  <<endl;
    return 0;
}

A Reference Takes its Own Space in Memory

We can see this by checking the size of the class which has only reference variables. The example below proofs that a C++ reference is not an alias and takes its own space into the memory.

C++
#include <iostream.h>

class Test
{
    int &i;   // int *const i;
    int &j;   // int *const j;
    int &k;   // int *const k; 
};

int main()
{    
    // This will print 12 i.e. size of 3 pointers
    cout<<  "size of class Test = "  <<   sizeof(class Test)  <<endl;
    return 0;
}

Conclusion

I hope that this article explains everything about C++ references. However I'd like to mention that C++ standard doesn't explain how reference behaviour should be implemented by the compiler. It's up to the compiler to decide, and most of the time it is implemented as a constant pointer.

Additional Notes to Support this Article

In the discussion forums for this article, people were having concerns that References are not constant pointers but aliases. I am writing one more example to support this fact. Look carefully at the example below:

C++
#include <iostream.h>

class A
{
public:
	virtual void print() { cout<<"A.."<<endl; }
};

class B : public A
{
public:
	virtual void print() { cout<<"B.."<<endl; }
};

class C : public B
{
public:
	virtual void print() { cout<<"C.."<<endl; }
};

int main()
{
	C c1;
	A &a1 = c1;
	a1.print(); // prints C

 	A a2 = c1;
	a2.print(); // prints A
	return 0;
}

The example using references supports the virtual mechanism, i.e. looking into the virtual pointer to get the handle to correct function pointer. The interesting thing here is how the virtual mechanism is supported by the static type which is simply an alias. Virtual mechanism is supported by dynamic information which will come into the picture only when a pointer is involved. I hope this will clarify most of the doubts.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Architect
India India
A programmer by heart since 1998. Written code in C++, Java, JavaScript, Python & Ruby, Worked on Stack Development to Web Development. Data Specialist with SQL and NoSQL DBs

Comments and Discussions

 
GeneralRe: Confusing article Pin
itsdkg5-Apr-06 18:56
itsdkg5-Apr-06 18:56 
GeneralRe: Confusing article Pin
jefito12-Apr-06 6:03
jefito12-Apr-06 6:03 
GeneralRe: Confusing article Pin
itsdkg18-Apr-06 19:34
itsdkg18-Apr-06 19:34 
GeneralRe: Confusing article Pin
Rainer Schuster18-Apr-06 21:14
Rainer Schuster18-Apr-06 21:14 
GeneralRe: Confusing article Pin
Iftahh19-Apr-06 2:24
Iftahh19-Apr-06 2:24 
GeneralRe: Confusing article Pin
Ilya Lipovsky28-Apr-06 11:54
Ilya Lipovsky28-Apr-06 11:54 
GeneralRe: Confusing article Pin
jefito1-May-06 7:32
jefito1-May-06 7:32 
GeneralRe: Confusing article Pin
Ilya Lipovsky1-May-06 13:13
Ilya Lipovsky1-May-06 13:13 
GeneralRe: Confusing article Pin
jefito2-May-06 3:26
jefito2-May-06 3:26 
Ilya Lipovsky wrote:
Before accusing me of being "confused," **please** do read the previous posts I wrote. In those posts I gave examples of gcc generating binaries wherein reference variables and original variables *do occupy* different memory locations.


Please feel free to note that what I actually said was that you "seem confused", and that was with respect to the role of optimization in compilers. It's an opinion, not an accusation, and subject to change, should you want to try to change my mind. Maybe I've misinterpreted what you said, but in prior posts, you insisted that I submit unoptimized generated code here. To what end, I can't understand -- the code would only tend to validate an entirely unsurprising conclusion: that references can be implemented as pointers. This is less strong than what the original article claims (as nearly as I can make out, because the article seems confused to me also), namely that references must be implemented as pointers. Your pursuit of the less surprising and hence, less interesting result led me to believe that you were confused on the role of optimization.

As for the rest, all noble words, indeed, but rather off the main point of the article, I think. In your prior post, you made assertions that I found questionable, and so I questioned you. For example, right at the start, you said:
The problem, however, is that whatever the standard says is not the way some very popular compilers implement the concept of references.


I found this very surprising, and asked you to clarify by naming the particular compilers, and how they differ from what the standard says about references. And what is this "concept of references" you mention? Can you actually back up what you assert?

Next, you made some claims about how a compiler must operate [snipped for brevity's sake]:
...the compiler is obligated to treat all reference variable declarations as const pointer declarations...


Again, I was surprised, and asked you to support your position. If "the compiler is obligated", then it is obligated to some set of rules (the Standard?). Who or what is it obligated to?

And so forth. You may theorize, ruminate, personally annotate, or whatever it is you think you're here for, but in the end, if you make concrete claims about the behavior of compilers vs. the Standard, you ought to be prepared to back them up. This is similar to my objections to Gatik's article wherein he claims that references are not aliases, and then can't or won't define what he means by the term 'alias'. The kindest interpretation that I can come up with for that type of behavior is "confusion".

regards,

Jeff
GeneralRe: Confusing article Pin
Ilya Lipovsky2-May-06 6:15
Ilya Lipovsky2-May-06 6:15 
GeneralRe: Confusing article Pin
jefito2-May-06 8:00
jefito2-May-06 8:00 
GeneralRe: Confusing article Pin
Ilya Lipovsky2-May-06 10:10
Ilya Lipovsky2-May-06 10:10 
GeneralRe: Confusing article Pin
jefito2-May-06 12:17
jefito2-May-06 12:17 
GeneralRe: Confusing article Pin
Ilya Lipovsky2-May-06 13:09
Ilya Lipovsky2-May-06 13:09 
GeneralRe: Confusing article Pin
jefito3-May-06 11:21
jefito3-May-06 11:21 
GeneralRe: Confusing article Pin
Ilya Lipovsky2-May-06 10:39
Ilya Lipovsky2-May-06 10:39 
GeneralRe: Confusing article Pin
jefito19-Apr-06 9:22
jefito19-Apr-06 9:22 
GeneralRe: Confusing article Pin
itsdkg12-May-06 3:40
itsdkg12-May-06 3:40 
GeneralRe: Confusing article Pin
jefito13-May-06 17:18
jefito13-May-06 17:18 
GeneralRe: Confusing article Pin
Androne19-Apr-06 5:09
Androne19-Apr-06 5:09 
GeneralRe: Confusing article Pin
Kamal Barshevich8-Apr-21 8:16
Kamal Barshevich8-Apr-21 8:16 
GeneralCertain Inaccuracies Found Pin
Ilya Lipovsky14-Mar-06 8:46
Ilya Lipovsky14-Mar-06 8:46 
GeneralRe: Certain Inaccuracies Found Pin
Paulius Maruka14-Mar-06 12:41
Paulius Maruka14-Mar-06 12:41 
GeneralRe: Certain Inaccuracies Found Pin
Ilya Lipovsky14-Mar-06 15:15
Ilya Lipovsky14-Mar-06 15:15 
GeneralRe: Certain Inaccuracies Found Pin
Ilya Lipovsky14-Mar-06 15:28
Ilya Lipovsky14-Mar-06 15:28 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.