Content deleted Content added
Line 63:
The fact that people use the term '''dynamic programming language''' in a variety of imprecise ways doesn't mean it has no precise definition. The current definition "execute at runtime many common behaviors that other languages might perform during compilation" is correct. No language is entirely static (performing all behaviors at compile time) or entirely dynamic (performing all behaviors at runtime), most languages group in the center between the two extremes, with a few outliers ranking highly static (C) or highly dynamic (Smalltalk). That said, it is useful to classify languages based on which dynamic features they include, and how many dynamic features they include. A table similar to those on [[Comparison of programming languages]] would be useful on this page, showing at least "dynamic compilation" (eval/closures/continuations/higher-order functions/self-modification/just-in-time), "dynamic dispatch" (symbolic/multiple dispatch/polymorphic inline caching), "dynamic typing" (not to be confused with weak/implicit, since dynamic type systems can also be strong/explicit), "dynamic loading" (library extension/inclusion/linking), "introspection" (access to meta-information about the source/internal details of the runtime environment). [[User:Allisonrandal|Allisonrandal]] ([[User talk:Allisonrandal|talk]]) 21:24, 13 September 2009 (UTC)
Closures, continuations & HOFs have nothing to do with "dynamic compilation". And why are macros mentioned in the article? In most languages they are purely a compile time feature.
I like to ride on motorcycle then read this, and you? :)
| |||