Runtime evaluation/In an environment: Difference between revisions

Being a stack-based language, there is usually no need to bind data stack objects to a variable name. This is the idiomatic way to do it, with <code>eval</code> referencing what it needs from the data stack:

However, to be pedantic about it, we can adhere to the letter of the task. Note that althoughAlthough we are using a dynamic variable for x, it exists in a temporary, non-global namespace. As far as I can tell, <code>eval</code> is unaware of surrounding lexical scope.