Quire

Mirror (programming)

From Quire, the open reference·Type of reflection mechanism in programming·1 min read

In computer programming, a mirror is a reflection mechanism that is completely decoupled from the object whose structure is being introspected. This is as opposed to traditional reflection, for example in Java, where one introspects an object using methods from the object itself (e.g. java.lang.Object::getClass() to get a java.lang.Class<?>).

Mirrors adhere to the qualities of encapsulation, stratification and ontological correspondence.[1]

Benefits#edit

Decoupling the reflection mechanism from the objects themselves allows for a few benefits:

  • The object's interface is not polluted, so there is no danger of breaking reflection by overriding a reflective method.
  • There can be different mirror systems.
  • The mirror system can be removed entirely (potentially allowing for optimizations).
  • A mirror system can operate on remote code, since it is not coupled with a particular machine.

Languages that use mirrors#edit

See also#edit

References#edit

  1. ^ Gilad Bracha and David Ungar, "Meta-level Facilities of Object-Oriented Programming languages"
  2. ^ cppreference.com. "std::meta::info". cppreference.com. Retrieved 19 May 2026.
  3. ^ "Frequently Asked Questions".
  4. ^ "Rubinius/Mirror.rb at master · rubinius/Rubinius".
  5. ^ The Rust Team (8 September 2026). "Struct Type". doc.rust-lang.org. The Rust Team.
  6. ^ "Environment, Universes, and Mirrors".

This article is mirrored from “Mirror (programming)” on English Wikipedia, revision 1375983066, written by Wikipedia's contributors and licensed CC BY-SA 4.0. Editing it here creates a Quire copy with its own history.

Synced with Wikipedia revision 1375983066 · just now