Dynamic programming language: Difference between revisions

Revision as of 16:59, 29 October 2022

Revision as of 09:43, 14 March 2023

Line 16:

===Eval===

Some dynamic languages offer an ''[[eval]]'' function. This function takes a string or [[abstract syntax tree]] containing code in the language and executes it. If this code stands for an expression, the resulting value is returned. [[Erik Meijer (computer scientist)|Erik Meijer]] and Peter Drayton distinguish the [[runtime code generation]] offered by eval from the [[dynamic loading]] offered by [[shared libraries]], and warn that in many cases eval is used merely to implement [[higher-order functionsfunction]]s (by passing functions as strings) or [[deserialization]].<ref>{{Citation | citeseerx = 10.1.1.69.5966 | title=Static Typing Where Possible, Dynamic Typing When Needed: The End of the Cold War Between Programming Languages | author=[[Erik Meijer (computer scientist)|Meijer, Erik]] and Peter Drayton | year=2005 | publisher=[[Microsoft]] Corporation|url=https://people.dsv.su.se/~beatrice/DYPL/meijer_drayton.pdf}}</ref>

===Object runtime alteration===

Line 28:

===Reflection===

[[Reflection (computer science)|Reflection]] is common in many dynamic languages, and typically involves [[Introspection (computer science)|analysis]] of the types and metadata of generic or [[Type polymorphism|polymorphic]] data. It can, however, also include full evaluation and modification of a program's code as data, such as the features that Lisp provides in analyzing [[S-expressionsexpression]]s.

===Macros===