The forced execution of souce code

How's called the ability of a language to interpret new code at runtime (the keyword/function that does this is typically called eval)?

For example Perl, Python, JavaScript and most shell languages have this. C and C++ haven't it.

Does Haskell have it? What about C#?

Note that shit like manually invoking the compiler doesn't count.

It's not just about executing "new" code, it's obvious you can do that in almost any language (however IMO it's an important distinction whether the language supports it natively or whether you have to manually supply an entire compiler implementation to do it).

What's interesting is
char buffa[9999];
i = 5;
gets(buffa);
eval(buffa);
printf("%d\n", i);
and then supporting an input like i += 1;

Obviously you're very fucked in C with normal compiled code, as the code itself has no notion of variable names, just to name the least of the problems.

So yeah, maybe you could call one type "dynamic" and the other "static", but I'm not sure this distinction and nomenclature are 100% right.

>>19
>Obviously you're very fucked in C with normal compiled code, as the code itself has no notion of variable names, just to name the least of the problems.
Not really... your eval function could just export i to the evalled program using plain old dynamic linking. Eval would prepend its input with "extern int i;" and everything would work great.

>>20
Only works for globals, can't do that for lexicals.

>>21
Why not? It isn't as automatic of course - you'd have to eval like eval(buffa, {{&i, "i", "int"}, {&j, "j", "long"}});, which is kind of ugly, but so is eval itself ;)