Reflection (computer programming)


In computer science, reflection is the ability of a process to examine, introspect, and modify its own structure and behavior.

Historical background

The earliest computers were programmed in their native assembly language, which were inherently reflective, as these original architectures could be programmed by defining instructions as data and using self-modifying code. As programming moved to compiled higher-level languages such as Algol, Cobol, and Fortran, this reflective ability largely disappeared until programming languages with reflection built into their type systems appeared.
Brian Cantwell Smith's 1982 doctoral dissertation introduced the notion of computational reflection in procedural programming languages and the notion of the meta-circular interpreter as a component of 3-Lisp.

Uses

Reflection helps programmers make generic software libraries to display data, process different formats of data, perform serialization or deserialization of data for communication, or do bundling and unbundling of data for containers or bursts of communication.
Effective use of reflection almost always requires a plan: A design framework, encoding description, object library, a map of a database or entity relations.
Reflection makes a language more suited to network-oriented code. For example, it assists languages such as Java to operate well in networks by enabling libraries for serialization, bundling and varying data formats. Languages without reflection have to use auxiliary compilers, e.g. for Abstract Syntax Notation, to produce code for serialization and bundling.
Reflection can be used for observing and modifying program execution at runtime. A reflection-oriented program component can monitor the execution of an enclosure of code and can modify itself according to a desired goal related to that enclosure. This is typically accomplished by dynamically assigning program code at runtime.
In object-oriented programming languages such as Java, reflection allows inspection of classes, interfaces, fields and methods at runtime without knowing the names of the interfaces, fields, methods at compile time. It also allows instantiation of new objects and invocation of methods.
Reflection is often used as part of software testing, such as for the runtime creation/instantiation of mock objects.
Reflection is also a key strategy for metaprogramming.
In some object-oriented programming languages, such as C# and Java, reflection can be used to bypass member accessibility rules. For C#-properties this can be achieved by writing directly onto the backing field of a non-public property. It is also possible to find non-public methods of classes and types and manually invoke them. This works for project-internal files as well as external libraries.

Implementation

A language supporting reflection provides a number of features available at runtime that would otherwise be difficult to accomplish in a lower-level language. Some of these features are the abilities to:
These features can be implemented in different ways. In MOO, reflection forms a natural part of everyday programming idiom. When verbs are called, various variables such as verb and this are populated to give the context of the call. Security is typically managed by accessing the caller stack programmatically: Since callers is a list of the methods by which the current verb was eventually called, performing tests on callers allows the verb to protect itself against unauthorised use.
Compiled languages rely on their runtime system to provide information about the source code. A compiled Objective-C executable, for example, records the names of all methods in a block of the executable, providing a table to correspond these with the underlying methods compiled into the program. In a compiled language that supports runtime creation of functions, such as Common Lisp, the runtime environment must include a compiler or an interpreter.
Reflection can be implemented for languages not having built-in reflection facilities by using a program transformation system to define automated source-code changes.

Examples

The following code snippets create an instance foo of class Foo and invoke its method PrintHello. For each programming language, normal and reflection-based call sequences are shown.

C#

The following is an example in C#:

// Without reflection
Foo foo = new Foo;
foo.PrintHello;
// With reflection
Object foo = Activator.CreateInstance;
MethodInfo method = foo.GetType.GetMethod;
method.Invoke;

Delphi

This Delphi example assumes that a TFoo class has been declared in a unit called Unit1:

uses RTTI, Unit1;
procedure WithoutReflection;
var
Foo: TFoo;
begin
Foo := TFoo.Create;
try
Foo.Hello;
finally
Foo.Free;
end;
end;
procedure WithReflection;
var
RttiContext: TRttiContext;
RttiType: TRttiInstanceType;
Foo: TObject;
begin
RttiType := RttiContext.FindType as TRttiInstanceType;
Foo := RttiType.GetMethod.Invoke.AsObject;
try
RttiType.GetMethod.Invoke;
finally
Foo.Free;
end;
end;

eC

The following is an example in eC:

// Without reflection
Foo foo ;
foo.hello;
// With reflection
Class fooClass = eSystem_FindClass;
Instance foo = eInstance_New;
Method m = eClass_FindMethod;
);

ECMAScript

The following is an example in ECMAScript, and therefore also applies to JavaScript and ActionScript:

// Without reflection
new Foo.hello
// With reflection
// assuming that Foo resides in this
new this
// or without assumption
new
// or simply
eval.hello')
// Using ECMAScript 2015's new Reflect class:
Reflect.construct

Go

The following is an example in Go:

import "reflect"
// Without reflection
f := Foo
f.Hello
// With reflection
fT := reflect.TypeOf
fV := reflect.New
m := fV.MethodByName
if m.IsValid

Java

The following is an example in Java:

import java.lang.reflect.Method;
// Without reflection
Foo foo = new Foo;
foo.hello;
// With reflection
try catch

Objective-C

The following is an example in Objective-C, implying either the OpenStep or Foundation Kit framework is used:

// Foo class.
@interface Foo : NSObject
- hello;
@end
// Sending "hello" to a Foo instance without reflection.
Foo *obj = Foo alloc] init];
;
// Sending "hello" to a Foo instance with reflection.
id obj = NSClassFromString alloc] init];
;

Perl

The following is an example in Perl:

  1. Without reflection
my $foo = Foo->new;
$foo->hello;
  1. or
Foo->new->hello;
  1. With reflection
my $class = "Foo"
my $constructor = "new";
my $method = "hello";
my $f = $class->$constructor;
$f->$method;
  1. or
$class->$constructor->$method;
  1. with eval
eval "new Foo->hello;";

PHP

The following is an example in PHP:

// Without reflection
$foo = new Foo;
$foo->hello;
// With reflection, using Reflections API
$reflector = new ReflectionClass;
$foo = $reflector->newInstance;
$hello = $reflector->getMethod;
$hello->invoke;

Python

The following is an example in Python:

  1. Without reflection
obj = Foo
obj.hello
  1. With reflection
obj = globals
getattr
  1. With eval
eval.hello')

R

The following is an example in R:

  1. Without reflection, assuming foo returns an S3-type object that has method "hello"
obj <- foo
hello
  1. With reflection
the.class <- "foo"
the.method <- "hello"
obj <- do.call)
do.call

Ruby

The following is an example in Ruby:

  1. Without reflection
obj = Foo.new
obj.hello
  1. With reflection
class_name = "Foo"
method_name = :hello
obj = Object.const_get.new
obj.send method_name
  1. With eval
eval "Foo.new.hello"

Xojo

The following is an example using Xojo:

' Without reflection
Dim fooInstance As New Foo
fooInstance.PrintHello
' With reflection
Dim classInfo As Introspection.Typeinfo = GetTypeInfo
Dim constructors As Introspection.ConstructorInfo = classInfo.GetConstructors
Dim fooInstance As Foo = constructors.Invoke
Dim methods As Introspection.MethodInfo = classInfo.GetMethods
For Each m As Introspection.MethodInfo In methods
If m.Name = "PrintHello" Then
m.Invoke
End If
Next

Citations