Category:Programming paradigm/Reflective: Difference between revisions

Content added Content deleted

Inline

Revision as of 21:29, 21 September 2009

A language is reflective if it includes features that allow it to ask about the current state of the program, e.g., by being able to inspect what classes are defined, what methods those classes define, or what instances of those classes have been created. This makes it far easier to write test harnesses and dynamic programs. However, one issue with reflective programming languages is that it is less clear when a part of the program has become actually unreachable as reflective techniques could be used to revive a reference to it.

Subcategories

This category has the following 19 subcategories, out of 19 total.

A

Apex‎ (1 C, 38 P)
Arturo‎ (1 C, 779 P)

B

BlitzMax‎ (3 C, 7 P)

C

C sharp‎ (3 C, 986 P)
Common Lisp‎ (3 C, 776 P)

E

Ecstasy‎ (64 P)

J

J‎ (3 C, 1,413 P)
Java‎ (3 C, 1,340 P)
Jinja‎ (4 P)

M

Maclisp‎ (3 P)

P

Perl‎ (6 C, 1,542 P)
Perl 6‎ (4 C)
PHP‎ (4 C, 471 P)
PowerShell‎ (3 C, 500 P)

R

Raku‎ (3 C, 1,619 P)
Ruby‎ (3 C, 1,236 P)

S

Smalltalk‎ (3 C, 325 P)

T

Tcl‎ (4 C, 983 P)
Trith‎ (3 C, 21 P)

Revision as of 12:59, 1 June 2009 (view source) rosettacode>Dkf No edit summary ← Older edit		Revision as of 21:29, 21 September 2009 (view source) rosettacode>Dkf (Added a basic description) Newer edit →
Line 1:		Line 1:
	{{feature\|Programming paradigm}}		{{feature\|Programming paradigm}}
			A language is reflective if it includes features that allow it to ask about the current state of the program, e.g., by being able to inspect what classes are defined, what methods those classes define, or what instances of those classes have been created. This makes it far easier to write test harnesses and dynamic programs. However, one issue with reflective programming languages is that it is less clear when a part of the program has become actually unreachable as reflective techniques could be used to revive a reference to it.