GeezerVison

This article needs more citations. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Boxing" computer programming – news · newspapers · books · scholar · JSTOR (August 2009) (Learn how and when to remove this message)

In computer science, boxing (a.k.a. wrapping) is the transformation of placing a primitive type within an object so that the value can be used as a reference. Unboxing is the reverse transformation of extracting the primitive value from its wrapper object. Autoboxing is the term for automatically applying boxing and/or unboxing transformations as needed.

Boxing's most prominent use is in Java where there is a distinction between reference and value types for reasons such as runtime efficiency and syntax and semantic issues. In Java, a java.util.LinkedList<T> must be such that T is an instance of java.lang.Object. One might desire to have a LinkedList<int> , but this is not directly possible. Instead Java defines primitive wrapper classes corresponding to each primitive type: java.lang.Integer and int , java.lang.Character and char , java.lang.Float and float , etc. Using generic parameterized types introduced in Java Platform, Standard Edition (J2SE) 5.0, one can then define a LinkedList<Integer> and insert int values into the list by boxing them as java.lang.Integer objects.

On the other hand, C# has no primitive wrapper classes, but allows boxing of any value type, returning a generic Object reference. In Objective-C, any primitive value can be prefixed by a @ to make an NSNumber out of it (e.g. @123 or @(123)). This allows for adding them in any of the standard collections, such as an NSArray.

Haskell has little or no notion of reference type, but still uses the term "boxed" for the runtime system's uniform pointer-to-tagged union representation.^[1]

The boxed object is always a copy of the value object, and is usually immutable. Unboxing the object also returns a copy of the stored value. Repeated boxing and unboxing of objects can have a severe performance impact, because boxing dynamically allocates new objects and unboxing (if the boxed value is no longer used) then makes them eligible for garbage collection. However, modern garbage collectors such as the default Java HotSpot garbage collector can more efficiently collect short-lived objects, so if the boxed objects are short-lived, the performance impact may not be severe.

In some languages, there is a direct equivalence between an unboxed primitive type and a reference to an immutable, boxed object type. In fact, it is possible to substitute all the primitive types in a program with boxed object types. Whereas assignment from one primitive to another will copy its value, assignment from one reference to a boxed object to another will copy the reference value to refer to the same object as the first reference. However, this will not cause any problems, because the objects are immutable, so there is semantically no real difference between two references to the same object or to different objects (unless using physical equality). For all operations other than assignment, such as arithmetic, comparison, and logical operators, one can unbox the boxed type, perform the operation, and re-box the result as needed. Thus, it is possible to not store primitive types at all.

Autoboxing is the term for getting a reference type out of a value type just through type conversion (either implicit or explicit). The compiler automatically supplies the extra source code that creates the object.

For example, in versions of Java prior to J2SE 5.0, the following code did not compile:

Integer i = new Integer(9);
Integer i = 9; // error in versions prior to 5.0!

Compilers prior to 5.0 would not accept the last line. java.lang.Integer are reference objects, on the surface no different from java.util.List, java.lang.Object, and so forth. To convert from an int to an java.lang.Integer, one had to "manually" instantiate the Integer object. As of J2SE 5.0, the compiler will accept the last line, and automatically transform it so that an Integer object is created to store the value 9 .^[2] This means that, from J2SE 5.0 on, something like Integer c = a + b , where a and b are java.lang.Integer themselves, will compile now — a and b are unboxed, the integer values summed up, and the result is autoboxed into a new java.lang.Integer, which is finally stored inside variable c. The equality operators cannot be used this way, because the equality operators are already defined for reference types, for equality of the references; to test for equality of the value in a boxed type, one must still manually unbox them and compare the primitives, or use the equals() static method in java.util.Objects.

Another example: J2SE 5.0 allows the programmer to treat a collection (such as a java.lang.LinkedList) as if it contained int values instead of java.lang.Integer objects. This does not contradict what was said above: the collection still only contains references to dynamic objects, and it cannot list primitive types. It cannot be a LinkedList<int> , but it must be a LinkedList<Integer> instead. However, the compiler automatically transforms the code so that the list will "silently" receive objects, while the source code only mentions primitive values. For example, the programmer can now write list.add(3) and think as if the int 3 were added to the list; but, the compiler will have actually transformed the line into list.add(new Integer(3)) .

Integer k = new Integer(4);
int l = k.intValue(); // always okay
int m = k; // would have been an error, but okay now

using System;

int i = 42;
object o = i; // box
int j = o; // unbox (error)
Console.WriteLine(j); // unreachable line, author might have expected output "42"

int i = 42;
Object o = i; // box
int j = o; // unbox (error)
System.out.println(j); // unreachable line, author might have expected output "42"

Rust has the std::boxed::Box<T> type, which represents a uniquely owned, heap-allocated value:^[3]

let number: Box<i32> = Box::new(42);

std::boxed::Box<T> in Rust is equivalent to std::unique_ptr<T> in C++, a kind of smart pointer.

using std::unique_ptr;

unique_ptr<int> number = std::make_unique<int>(42);

If the value needs to have shared ownership (e.g. between threads), one can use std::sync::Arc<T>, which represents a reference-counted, heap-allocated value.^[4][5] This is similar to std::shared_ptr<T> in C++.

Modern Object Pascal has yet another way to perform operations on simple types, close to boxing, called type helpers in Free Pascal or record helpers in Delphi and Free Pascal in Delphi mode.

The dialects mentioned are Object Pascal compile-to-native languages, and so lack some features that C# and Java can implement. Notably run-time type inference on strongly typed variables.

However, the feature is related to boxing. It allows using constructs like:

{$ifdef fpc}{$mode delphi}{$endif}
uses sysutils;  // this unit contains wraps for the simple types
var
  x:integer=100;
  s:string;
begin
  s:= x.ToString;
  writeln(s);
end.