Metaprogramming

Source: Wikipedia, the free encyclopedia.

Metaprogramming is a programming technique in which computer programs have the ability to treat other programs as their data. It means that a program can be designed to read, generate, analyse or transform other programs, and even modify itself while running.[1][2] In some cases, this allows programmers to minimize the number of lines of code to express a solution, in turn reducing development time.[3] It also allows programs a greater flexibility to efficiently handle new situations without recompilation.

Metaprogramming can be used to move computations from

reflection.[4]
Reflection is a valuable language feature to facilitate metaprogramming.

Metaprogramming was popular in the 1970s and 1980s using list processing languages such as

LISP. LISP hardware machines were popular in the 1980s and enabled applications that could process code. They were frequently used for artificial intelligence
applications.

Approaches

Metaprogramming enables developers to write programs and develop code that falls under the

first-class data type (as in Lisp, Prolog, SNOBOL, or Rebol) is also very useful; this is known as homoiconicity. Generic programming invokes a metaprogramming facility within a language by allowing one to write code without the concern of specifying data types since they can be supplied as parameters
when used.

Metaprogramming usually works in one of three ways.[5]

  1. The first approach is to expose the internals of the run-time engine to the programming code through
    IL
    emitter.
  2. The second approach is dynamic execution of expressions that contain programming commands, often composed from strings, but can also be from other methods using arguments or context, like JavaScript.[6] Thus, "programs can write programs." Although both approaches can be used in the same language, most languages tend to lean toward one or the other.
  3. The third approach is to step outside the language entirely. General purpose program transformation systems such as compilers, which accept language descriptions and carry out arbitrary transformations on those languages, are direct implementations of general metaprogramming. This allows metaprogramming to be applied to virtually any target language without regard to whether that target language has any metaprogramming abilities of its own. One can see this at work with Scheme and how it allows tackling some limitations faced in C by using constructs that were part of the Scheme language itself to extend C.[7]

RemObjects’ Pascal Script for Object Pascal
.

Usages

Code generation

A simple example of a metaprogram is this

generative programming
:

#!/bin/sh
# metaprogram
echo '#!/bin/sh' > program
for i in $(seq 992)
do
    echo "echo $i" >> program
done
chmod +x program

This script (or program) generates a new 993-line program that prints out the numbers 1–992. This is only an illustration of how to use code to write more code; it is not the most efficient way to print out a list of numbers. Nonetheless, a programmer can write and execute this metaprogram in less than a minute, and will have generated over 1000 lines of code in that amount of time.

A quine is a special kind of metaprogram that produces its own source code as its output. Quines are generally of recreational or theoretical interest only.

Not all metaprogramming involves generative programming. If programs are modifiable at runtime or if incremental compilation is available (such as in

REBOL, Ruby, Rust, R, SAS, Smalltalk, and Tcl
), then techniques can be used to perform metaprogramming without actually generating source code.

One style of generative approach is to employ

lex and yacc, two tools used to generate lexical analysers and parsers, let the user describe the language using regular expressions and context-free grammars
, and embed the complex algorithms required to efficiently parse the language.

Code instrumentation

One usage of metaprogramming is to instrument programs in order to do dynamic program analysis.

Challenges

Some argue that there is a sharp learning curve to make complete use of metaprogramming features.[8] Since metaprogramming gives more flexibility and configurability at runtime, misuse or incorrect use of metaprogramming can result in unwarranted and unexpected errors that can be extremely difficult to debug to an average developer. It can introduce risks in the system and make it more vulnerable if not used with care. Some of the common problems, which can occur due to wrong use of metaprogramming are inability of the compiler to identify missing configuration parameters, invalid or incorrect data can result in unknown exception or different results.[9] Due to this, some believe[8] that only high-skilled developers should work on developing features which exercise metaprogramming in a language or platform and average developers must learn how to use these features as part of convention.

Uses in programming languages

Macro systems

Macro assemblers

The

macro assembler facilities that were often used to generate complete assembly language programs [citation needed] or sections of programs (for different operating systems for instance). Macros provided with CICS transaction processing system had assembler macros that generated COBOL
statements as a pre-processing step.

Other assemblers, such as

MASM
, also support macros.

Metaclasses

Metaclasses are provided by the following programming languages:

Template metaprogramming

Staged metaprogramming

Dependent types

Usage of dependent types allows proving that generated code is never invalid.[15] However, this approach is bleeding-edge and is rarely found outside of research programming languages.

Implementations

The list of notable metaprogramming systems is maintained at

List of Program Transformation Systems
.

See also

References

  1. ^ Harald Sondergaard. "Course on Program Analysis and Transformation". Retrieved 18 September 2014.
  2. .
  3. ^ Walker, Max. "The Art of Metaprogrmming in Java". New Circle. Retrieved 28 January 2014.
  4. ^ Krauss, Aaron. "Programming Concepts: Type Introspection and Reflection". The Societa. Retrieved 14 September 2014.
  5. ^ Joshi, Prateek (5 April 2014). "What Is Metaprogramming? – Part 2/2". Perpetual Enigma. Retrieved 14 August 2014.
  6. ^ for example, instance_eval in Ruby takes a string or an anonymous function. "Rdoc for Class: BasicObject (Ruby 1.9.3) - instance_eval". Retrieved 30 December 2011.
  7. ^ "Art of Metaprogramming". IBM.
  8. ^ a b Bicking, Ian. "The challenge of metaprogramming". IanBicking.org. Retrieved 21 September 2016.
  9. ^ Terry, Matt (21 August 2013). "Beware of Metaprogramming". Medium.com. Medium Corporation. Retrieved 21 August 2014.
  10. ^ Through Common Lisp Object System's "Meta Object Protocol"
  11. ^ "C++ Template Metaprogramming". aszt.inf.elte.hu. Retrieved 2022-07-23.
  12. ^ Lisp (programming language) "Self-evaluating forms and quoting", quasi-quote operator.
  13. ^ "LMS: Program Generation and Embedded Compilers in Scala". scala-lms.github.io. Retrieved 2017-12-06.
  14. S2CID 52898203
    .
  15. . Retrieved 29 August 2012.

External links