C++ Reference Type Assignment

The latest version of this topic can be found at C++ Stack Semantics for Reference Types.

Prior to Visual C++ 2005, an instance of a reference type could only be created using the operator, which created the object on the garbage collected heap. However, you can now create an instance of a reference type using the same syntax that you would use to create an instance of a native type on the stack. So, you do not need to use ref new, gcnew to create an object of a reference type. And when the object goes out of scope, the compiler calls the object's destructor.

When you create an instance of a reference type using stack semantics, the compiler does internally create the instance on the garbage collected heap (using ).

When the signature or return type of a function includes an instance of a by-value reference type, the function will be marked in the metadata as requiring special handling (with modreq). This special handling is currently only provided by Visual C++ clients; other languages do not currently support consuming functions or data that use reference types created with stack semantics.

One reason to use (dynamic allocation) instead of stack semantics would be if the type has no destructor. Also, using reference types created with stack semantics in function signatures would not be possible if you want your functions to be consumed by languages other than Visual C++.

The compiler will not generate a copy constructor for a reference type. Therefore, if you define a function that uses a by-value reference type in the signature, you must define a copy constructor for the reference type. A copy constructor for a reference type has a signature of the following form: .

The compiler will not generate a default assignment operator for a reference type. An assignment operator allows you to create an object using stack semantics and initialize it with an existing object created using stack semantics. An assignment operator for a reference type has a signature of the following form: .

If your type's destructor releases critical resources and you use stack semantics for reference types, you do not need to explicitly call the destructor (or call ). For more information on destructors in reference types, see Destructors and Finalizers in Visual C++.

A compiler-generated assignment operator will follow the usual standard C++ rules with the following additions:

  • Any non-static data members whose type is a handle to a reference type will be shallow copied (treated like a non-static data member whose type is a pointer).

  • Any non-static data member whose type is a value type will be shallow copied.

  • Any non-static data member whose type is an instance of a reference type will invoke a call to the reference type’s copy constructor.

The compiler also provides a unary operator to convert an instance of a reference type created using stack semantics to its underlying handle type.

The following reference types are not available for use with stack semantics:

Description

The following code sample shows how to declare instances of reference types with stack semantics, how the assignment operator and copy constructor works, and how to initialize a tracking reference with reference type created using stack semantics.

Code

Output

Classes and Structs

// stack_semantics_for_reference_types.cpp // compile with: /clr ref class R { public: int i; R(){} // assignment operator void operator=(R% r) { i = r.i; } // copy constructor R(R% r) : i(r.i) {} }; void Test(R r) {} // requires copy constructor int main() { R r1; r1.i = 98; R r2(r1); // requires copy constructor System::Console::WriteLine(r1.i); System::Console::WriteLine(r2.i); // use % unary operator to convert instance using stack semantics // to its underlying handle R ^ r3 = %r1; System::Console::WriteLine(r3->i); Test(r1); R r4; R r5; r5.i = 13; r4 = r5; // requires a user-defined assignment operator System::Console::WriteLine(r4.i); // initialize tracking reference R % r6 = r4; System::Console::WriteLine(r6.i); }


C++ References

C++ references allow you to create a second name for the a variable that you can use to read or modify the original data stored in that variable. While this may not sound appealing at first, what this means is that when you declare a reference and assign it a variable, it will allow you to treat the reference exactly as though it were the original variable for the purpose of accessing and modifying the value of the original variable--even if the second name (the reference) is located within a different scope. This means, for instance, that if you make your function arguments references, and you will effectively have a way to change the original data passed into the function. This is quite different from how C++ normally works, where you have arguments to a function copied into new variables. It also allows you to dramatically reduce the amount of copying that takes place behind the scenes, both with functions and in other areas of C++, like catch clauses.

Basic Syntax

Declaring a variable as a reference rather than a normal variable simply entails appending an ampersand to the type name, such as this "reference to an int" int& foo = ....; Did you notice the "...."? (Probably, right? After all, it's 25% of the example.) When a reference is created, you must tell it which variable it will become an alias for. After you create the reference, whenever you use the variable, you can just treat it as though it were a regular integer variable. But when you create it, you must initialize it with another variable, whose address it will keep around behind the scenes to allow you to use it to modify that variable.

In a way, this is similar to having a pointer that always points to the same thing. One key difference is that references do not require dereferencing in the same way that pointers do; you just treat them as normal variables. A second difference is that when you create a reference to a variable, you need not do anything special to get the memory address. The compiler figures this out for you: int x; int& foo = x; // foo is now a reference to x so this sets x to 56 foo = 56; std::cout << x <<std::endl;

Functions taking References Parameters

Here's a simple example of setting up a function to take an argument "by reference", implementing the swap function: void swap (int& first, int& second) { int temp = first; first = second; second = temp; } Both arguments are passed "by reference"--the caller of the function need not even be aware of it: int a = 2; int b = 3; swap( a, b ); After the swap, a will be 3 and b will be 2. The fact that references require no extra work can lead to confusion at times when variables magically change after being passed into a function. Bjarne Stroustrup suggests that for arguments that the function is expected to change, using a pointer instead of a reference helps make this clear--pointers require that the caller explicitly pass in the memory address.

Efficiency Gains

You might wonder why you would ever want to use references other than to change the value--well, the answer is that passing by reference means that the variable need not be copied, yet it can still be passed into a function without doing anything special. This gives you the most bang for your buck when working with classes. If you want to pass a class into a function, it almost always makes sense for the function to take the class "by reference"--but generally, you want to use a const reference.

This might look something like this: int workWithClass( const MyClass& a_class_object ) { } The great thing about using const references is that you can be sure that the variable isn't modified, so you can immediately change all of your functions that take large objects--no need to make a copy anymore. And even you were conscientious and used pointers to pass around large objects, using references in the future can still make your code that much cleaner.

References and Safety

You're probably noticing a similarity to pointers here--and that's true, references are often implemented by the compiler writers as pointers. A major difference is that references are "safer". In general, references should always be valid because you must always initialize a reference. This means that barring some bizarre circumstances (see below), you can be certain that using a reference is just like using a plain old non-reference variable. You don't need to check to make sure that a reference isn't pointing to NULL, and you won't get bitten by an uninitialized reference that you forgot to allocate memory for.

References and Safety: the Exceptions

For the sake of full disclosure, it is possible to have an invalid references in one minor and one major case.

First, if you explicitly assign a reference to a dereferenced NULL pointer, your reference will be invalid: int *x = 0; int& y = *x; Now when you try to use the reference, you'll get a segmentation fault since you're trying to access invalid memory (well, on most systems anyhow).

By the way, this actually does work: since you're not actually accessing the value stored in *x when you make the reference to it, this will compile just fine.

A more pressing issue is that it is possible to "invalidate" a reference in the sense that it is possible that a reference to a block of memory can live on past the time when the memory is valid. The most immediate example is that you shouldn't return a reference to local memory: int& getLocalVariable() { int x; return x; } Once the stack frame containing the memory for getLocalVariable is taken off the stack, then the reference returned by this function will no longer be valid. Oops.

References and Dynamically Allocated Memory

Finally, beware of references to dynamically allocated memory. One problem is that when you use references, it's not clear that the memory backing the reference needs to be deallocated--it usually doesn't, after all. This can be fine when you're passing data into a function since the function would generally not be responsible for deallocating the memory anyway.

On the other hand, if you return a reference to dynamically allocated memory, then you're asking for trouble since it won't be clear that there is something that needs to be cleaned up by the function caller.

0 comments

Leave a Reply

Your email address will not be published. Required fields are marked *