Runtime evaluation: Difference between revisions
Content added Content deleted
(→{{header|Lasso}}: Adding Lasso explanation and example) |
(→{{header|Common Lisp}}: Add Déjà Vu example) |
||
| Line 257: | Line 257: | ||
===Debugging Notes=== |
===Debugging Notes=== |
||
There are no standardized debugging facilities specific to the <code>eval</code> operation itself, but code evaluted may be affected by the current [http://www.lispworks.com/documentation/HyperSpec/Body/03_c.htm global declarations], particularly the [http://www.lispworks.com/documentation/HyperSpec/Body/d_optimi.htm <code>optimize</code> declaration]'s <code>debug</code> and <code>safety</code> qualities. |
There are no standardized debugging facilities specific to the <code>eval</code> operation itself, but code evaluted may be affected by the current [http://www.lispworks.com/documentation/HyperSpec/Body/03_c.htm global declarations], particularly the [http://www.lispworks.com/documentation/HyperSpec/Body/d_optimi.htm <code>optimize</code> declaration]'s <code>debug</code> and <code>safety</code> qualities. |
||
=={{header|Déjà Vu}}== |
|||
The compiler, module system and interactive interpreter are all implemented in Déjà Vu itself, and the first two are part of the standard library. |
|||
Each compiled fragment is considered to be a single "file", and cannot access any local variables from outside of itself. |
|||
<lang dejavu>!run-blob !compile-string "(fake filename)" "!print \qHello world\q"</lang> |
|||
{{out}} |
|||
<pre>Hello world</pre> |
|||
=={{header|E}}== |
=={{header|E}}== |
||