Runtime evaluation

From Rosetta Code
Jump to: navigation, search
Task
Runtime evaluation
You are encouraged to solve this task according to the task description, using any language you may know.
Demonstrate your language's ability for programs to execute code written in the language provided at runtime. Show us what kind of program fragments are permitted (e.g. expressions vs. statements), how you get values in and out (e.g. environments, arguments, return values), if applicable what lexical/static environment the program is evaluated in, and what facilities for restricting (e.g. sandboxes, resource limits) or customizing (e.g. debugging facilities) the execution.

You may not invoke a separate evaluator program, or invoke a compiler and then its output, unless the interface of that program, and the syntax and means of executing it, are considered part of your language/library/platform.

For a more constrained task giving a specific program fragment to evaluate, see Eval in environment.

Contents

[edit] ALGOL 68

Works with: ALGOL 68G version Any - tested with release mk15-0.8b.fc9.i386 - this implementation is an interpretor, and evaluate is an extension to the standard

Variable names are generally not visible at run time with classic compilers. However ALGOL 68G is an interpretor and it retains this ability.

print(evaluate("4.0*arctan(1.0)"))

Output:

+3.14159265358979e  +0

This example demonstrates the use of variables and that the Algol 68G evaluate uses the normal Algol 68 scoping rules:

Works with: ALGOL 68G version tested with release 2.8.win32
# procedure to call the Algol 68G evaluate procedure                    #
# the environment of the evaluation will be the caller's environment #
# with "code", "x" and "y" defined as the procedure parameters #
PROC ev = ( STRING code, INT x, INT y )STRING: evaluate( code );
 
BEGIN
 
INT i := 1;
INT j := 2;
REAL x := 4.2;
REAL y := 0.7164;
 
# evaluates "i + j" in the current environment #
print( ( evaluate( "i + j" ), newline ) );
 
# evaluates "x + y" in the environment of the procedure body of ev #
print( ( ev( "x + y", i, j ), newline ) );
 
# evaluates "x + y" in the current environment, so shows a different #
# result to the previous call #
print( ( evaluate( "x + y" ), newline ) );
 
# prints "code" because code is defined in the environment of the #
# call to evaluate (in ev) although it is not defined in this #
# environment #
print( ( ev( "code", 1, 2 ), newline ) );
 
# prints "code + codecode + code" - see above #
print( ( ev( "code + code", 1, 2 ), newline ) )
 
END
 
# if this next call was executed, a runtime error would occur as x and y #
# do not exist anymore #
# ;print( ( evaluate( "x + y" ), newline ) ) #

Output:

         +3
         +3
+4.91640000000000e  +0
code
code + codecode + code

[edit] AutoHotkey

Works with: AutoHotkey_H

function addScript can be used to dynamically add lines of code to a running script.

; requires AutoHotkey_H or AutoHotkey.dll
msgbox % eval("3 + 4")
msgbox % eval("4 + 4")
return
 
 
eval(expression)
{
global script
script =
(
expression(){
return %expression%
}
)
renameFunction("expression", "") ; remove any previous expressions
gosub load ; cannot use addScript inside a function yet
exp := "expression"
return %exp%()
}
 
load:
DllCall(A_AhkPath "\addScript","Str",script,"Uchar",0,"Cdecl UInt")
return
 
renameFunction(funcName, newname){
static
x%newname% := newname ; store newname in a static variable so its memory is not freed
strput(newname, &x%newname%, strlen(newname) + 1)
if fnp := FindFunc(funcName)
numput(&x%newname%, fnp+0, 0, "uint")
}

[edit] BASIC

Works with: Beta BASIC version 3.0

Works with: SAM BASIC

[edit] Evaluating expressions

VAL() function converts string into numeric value. On many Basic implementations, VAL only accepts simple numeric values. However, Sinclair Basic and its derivates such as Beta Basic and SAM Basic accept any expression that evaluates to numeric value.

The following example shows a functon that plots graph of any function f(x). The function is passed in string parameter f$.

100 DEF PROC graph f$
110   LOCAL x,y
120   PLOT 0,90
130   FOR x = -2 TO 2 STEP 0.02
140     LET y = VAL(f$)
150     DRAW TO x*50+100, y*50+90
160   NEXT x
170 END PROC

Usage example:

500 graph "SIN(x) + SIN(x*3)/3"

[edit] Executing code

The KEYIN statement available on Beta Basic and SAM Basic executes a string as if it had been entered from keyboard in command mode. It can execute commands directly, or add (or replace) lines in the program while the program is executing. This allows creating self-modifying programs.

The function do_with_x in the following example loops variable x from 1 to 10 and within the loop executes any code passed to function in parameter p$.

100 DEF PROC do_with_x p$
110   LOCAL x
130   FOR x = 1 TO 10
140     KEYIN p$
160   NEXT x
170 END PROC

The usage example below creates a multiplication table by executing inner loop for y:

500 LET y$ = "FOR y=1 TO 10: PRINT AT y, x*3; x*y: NEXT y"
510 do_with_x y$

VAL and KEYIN execute code in the environment they are called from. In the above examples, VAL and KEYIN both see the local variable x. There is no sandbox functionality in Bata BASIC or SAM BASIC.

[edit]
Works with: ZX Spectrum Basic

In ZX Spectrum Basic, loading a new program will replace the existing program. The new program will sutomatically run, if it was saved to do so by using SAVE together with LINE:

 
10 REM load the next program
20 LOAD "PROG2"
 

[edit] BBC BASIC

[edit] Expressions

Expressions can be evaluated using the EVAL function:

      expr$ = "PI^2 + 1"
PRINT EVAL(expr$)

Output:

10.8696044

[edit] Statements

Statements can be executed by being tokenised and then written to a temporary file:

      exec$ = "PRINT ""Hello world!"""
bbc$ = FNtokenise(exec$)
 
tmpfile$ = @tmp$+"temp.bbc"
tmpfile% = OPENOUT(tmpfile$)
BPUT#tmpfile%, bbc$+CHR$0
CLOSE #tmpfile%
 
CALL tmpfile$
END
 
DEF FNtokenise(A$)
LOCAL A%
A% = EVAL("0:"+A$)
A$ = $(!332+2)
= CHR$(LENA$+4) + CHR$0 + CHR$0 + A$ + CHR$13
 

Output:

Hello world!

[edit] Burlesque

In Burlesque "Code" is actually just a list of identifiers. It is therefore possible to create and manipulate code at runtime. Evaluating a block:

 
blsq ) {5 5 .+}e!
10
 

Creating code at runtime (changing map (+5) to map (+6) at runtime):

 
blsq ) 1 10r@{5.+}m[
{6 7 8 9 10 11 12 13 14 15}
blsq ) 1 10r@{5.+}6 0sam[
{7 8 9 10 11 12 13 14 15 16}
 

Code from string at runtime:

 
blsq ) 1 10r@"5.+"psm[
{6 7 8 9 10 11 12 13 14 15}
 

Evaluating strings at runtime (reverse is just for demonstration):

 
blsq ) "[m}+.5{@r01 1"<-pe
{6 7 8 9 10 11 12 13 14 15}
 

Injecting other functions into code:

 
blsq ) {3 2}(?*)[+e!
6
 

Identifiers not contained in a block require to be quoted to push them to the stack. Note the difference:

 
blsq ) ?+
ERROR: Burlesque: (.+) Invalid arguments!
blsq ) ?+to
"Error"
blsq ) (?+)
?+
blsq ) (?+)to
"Ident"
 

(also note the fallback to .+ from ?+).

[edit] Caché ObjectScript

The 'XECUTE' command performs substantially the same operation as the '$XECUTE' function, except the latter must specify a return value.

Examples:
USER>Set cmd="Write ""Hello, World!"""
USER>Xecute cmd
Hello, World!

USER>Set fnc="(num1, num2) Set res=num1+num2 Quit res"
USER>Write $Xecute(fnc, 2, 3)
5

[edit] Common Lisp

[edit] Brief eval tutorial

The eval function evaluates Lisp code at runtime.

(eval '(+ 4 5)) ; returns 9

In Common Lisp, programs are represented as trees (s-expressions). Therefore, it is easily possible to construct a program which includes externally specified values, particularly using backquote template syntax:

(defun add-four-complicated (a-number)
(eval `(+ 4 ',a-number)))

Or you can construct a function and then call it. (If the function is used more than once, it would be good to use compile instead of eval, which compiles the code before returning the function. eval is permitted to compile as well, but compile requires it.)

(defun add-four-by-function (a-number)
(funcall (eval '(lambda (n) (+ 4 n)))) a-number)

If your program came from a file or user input, then you have it as a string, and read or read-from-string will convert it to s-expression form:

(eval (read-from-string "(+ 4 5)"))

Common Lisp has lexical scope, but eval always evaluates “in the null lexical environment”. In particular, eval does not inherit the lexical variables from the enclosing code. (Note that eval is an ordinary function and as such does not have access to that environment anyway.)

(let ((x 11) (y 22))
;; This is an error! Inside the eval, x and y are unbound!
(format t "~%x + y = ~a" (eval '(+ x y))))

One way to fix the error is to (declare (special x y)) for dynamic variables; but the easier and shorter way is to insert the values of x and y with the backquote template syntax.

(let ((x 11) (y 22))
(format t "~%x + y = ~a" (eval `(+ ,x ,y))))

[edit] Sandboxing Discussion

Sandboxing in Common Lisp can be approached in a variety of ways, none of which are standardized.

One approach to define a sublanguage and validate expressions before passing them to compile or eval. Of course, a whole different language entirely can be defined, and translated to Lisp. This is essentially the classic "trusted compiler generating safe code in an untrusted target language" approach.

One way to simplify the validator is to use the package system to create a sandbox. This is done by defining a package arbitrarily called sandbox. The validator then simply has to make sure that all symbols used in the expression are restricted to those which are visible inside the sandbox package. Inside sandbox, we include only those functions, operators, variables and other symbols from system packages that are safe: materials which don't allow sandboxed code to do anything harmful from within the sandbox, or to escape from the sandbox. For instance, suppose that some package system has a function called run-shell-command. We do not import run-shell-command into the sandbox package, and our validator will reject code which has references such as
(system:run-shell-command ...)
. Therefore, the sandboxed code has no direct way to run that function. To gain access to it, it must exploit some flaw in the sandbox. One flaw in the sandbox would be the inclusion of certain package-related functions like find-symbol. The expression
(find-symbol "FOO" "BAR")
will retrieve symbol foo::bar if it exists. The validator will not find this code because it has no embedded symbolic references to package foo; they are disguised as character string. A cautious approach to the sandbox should be taken: include less rather than more, and consider each expansion of the sandbox with meticulous care.

[edit] Debugging Notes

There are no standardized debugging facilities specific to the eval operation itself, but code evaluted may be affected by the current global declarations, particularly the optimize declaration's debug and safety qualities.

[edit] 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.

!run-blob !compile-string "(fake filename)" "!print \qHello world\q"
Output:
Hello world

[edit] E

In E, eval is a method of expression ASTs (EExprs). (Other types of program fragment ASTs such as methods and patterns may not be directly evaluated, and must be inserted into an expression.)

The lexical environment is provided as a parameter and cannot be omitted. The evaluated program has no access to anything but the provided environment.

? e`1 + 1`.eval(safeScope)
# value: 2

eval returns the value of the expression. evalToPair also returns the modified environment for use with further evaluation, e.g. for implementing a REPL.

? def [value, env] := e`def x := 1 + 1`.evalToPair(safeScope)
# value: [2, ...]
 
? e`x`.eval(env)
# value: 2

Eval from a string may be done by invoking the parser.

? def prog := <elang:syntax.makeEParser>.run("1 + 1")
# value: e`1.add(1)`
 
? prog.eval(safeScope)
# value: 2

[edit] Erlang

Erlang eval is a bit complex/verbose and requires the interaction of 3 modules: erl_scan (tokenizes), erl_parse (returns an abstract form) and erl_eval (variable binding, evaluate abstract form, etc).

1> {ok, Tokens, _} = erl_scan:string("X + 4 * lists:sum([1,2,3,4]).").
...
2> {ok, [Form]} = erl_parse:parse_exprs(Tokens).
...
3> Bindings = erl_eval:add_binding('X', 17, erl_eval:new_bindings()).
[{'X',17}]
4> {value, Value, _} = erl_eval:expr(Form, Bindings).
{value,57,[{'X',17}]}
5> Value.
57
 

[edit] Forth

EVALUATE invokes the interpreter on a string of Forth code, using and modifying the current dictionary and stack state.

s" variable foo   1e fatan 4e f*" evaluate
 
f. \ 3.14159...
1 foo !

Sandboxing can be achieved in general by using MARKER, which defines a checkpoint for the dictionary state which can later be restored.

unused .    \ show how much dictionary space is available
marker restore
 
create foo 30 allot
: my-def 30 0 do cr i . ." test" loop ;
 
unused . \ lower than before
 
restore
unused . \ same as first unused; restore, foo, and my-def no longer defined

[edit] Go

As a compiled, strongly typed language, eval() is not the strong suit of Go. Nevertheless, an eval package exists that does that. Just don't expect it to be as easy or efficient as in interpreted languages. The eval package was originally part of the Go standard library but is now hosted and maintained externally.

package main
import (
"fmt"
"bitbucket.org/binet/go-eval/pkg/eval"
"go/token"
)
 
func main() {
w := eval.NewWorld();
fset := token.NewFileSet();
 
code, err := w.Compile(fset, "1 + 2")
if err != nil {
fmt.Println("Compile error");
return
}
 
val, err := code.Run();
if err != nil {
fmt.Println("Run time error");
return;
}
fmt.Println("Return value:", val) //prints, well, 3
 
}

[edit] Groovy

Each of these solutions evaluates a Groovy script based on some variation of the solution to the "Yuletide Holiday" task. Each variation has been verified to give the same output:

[2011, 2016, 2022, 2033, 2039, 2044, 2050, 2061, 2067, 2072, 2078, 2089, 2095, 2101, 2107, 2112, 2118]

[edit] Simple evaluation

The GroovyShell class allows the evaluation of a string or of the text contents of a File or InputStream as a Groovy script. A script is a either a set of statements to be executed in order, or a Groovy class with a main() method, or a Groovy Thread subclass or Runnable implementation. The return value is the value of the last statement executed, or the value of an explicit return statement (if any).

def years1 = new GroovyShell().evaluate('''
(2008..2121).findAll {
Date.parse("yyyy-MM-dd", "${it}-12-25").format("EEE") == "Sun"
}
'''
)
 
println years1

The last expression evaluated in the script, a list of years found, is the return value of the evaluate() method.

[edit] Evaluation with variables

There are several approaches to evaluating a script with variables:

  • GString embedded values
  • Binding variables
  • Eval shortcut

GString embedded values
Setting up the script as a GString with embedded value parsing is a "natural" ad hoc solution for Groovy programmers, but there are possible pitfalls if the script itself contains GStrings.

def startYear = 2008
def endYear = 2121
def years2 = new GroovyShell().evaluate("""
(${startYear}..${endYear}).findAll {
Date.parse("yyyy-MM-dd", "\${it}-12-25").format("EEE") == "Sun"
}
"""
)
 
println years2

The variables "startYear" and "endYear" are dynamically pulled into the script GString as embedded values before the script itself ever executes.

Notice that in the script the embedded value "${it}" must be quoted with backslash (\) to prevent parsing as a part of the script GString. However, it is still correctly parsed within the internal GString when the script is run.

Binding variables
GroovyShell uses a Binding object to pass variable values to a script. This is the only way to pass variables if the script comes from a File or InputStream, but even if the script is a string Binding avoids the nested quoting issue caused by the ad hoc use of GString.

def context = new Binding()
context.startYear = 2008
context.endYear = 2121
def years3 = new GroovyShell(context).evaluate('''
(startYear..endYear).findAll {
Date.parse("yyyy-MM-dd", "${it}-12-25").format("EEE") == "Sun"
}
'''
)

We may instantiate Binding with the variables as named parameters, allowing a more terse syntax:

def years4 = new GroovyShell( new Binding(startYear: 2008, endYear: 2121) ).evaluate('''
(startYear..endYear).findAll {
Date.parse("yyyy-MM-dd", "${it}-12-25").format("EEE") == "Sun"
}
'''
)
 
println years4

We may also access the Binding object after script evaluation to extract values of any global variables set during the evaluation:

def binding = new Binding(startYear: 2008, endYear: 2121)
new GroovyShell( binding ).evaluate('''
yearList = (startYear..endYear).findAll {
Date.parse("yyyy-MM-dd", "${it}-12-25").format("EEE") == "Sun"
}
'''
)
 
println binding.yearList

Eval shortcut
For simple evaluation of string-based scripts with only a few variables (like this one), the Eval class has static shortcut methods that do the Binding setup and GroovyShell evaluation under the surface. Eval.me(script) evaluates a script with no variables. Eval.x(x,script), Eval.xy(x,y,script), or Eval.xyz(x,y,z,script) each evaluates a script with 1, 2, or 3 variables, respectively. Here is an example with start and end years as script variables x and y.

def years5 = Eval.xy(2008, 2121, '''
(x..y).findAll {
Date.parse("yyyy-MM-dd", "${it}-12-25").format("EEE") == "Sun"
}
'''
)
 
println years5

[edit] GW-BASIC

10 LINE INPUT "Type an expression: ",A$
20 OPEN "CHAIN.TMP" FOR OUTPUT AS #1
30 PRINT #1, "70 LET Y=("+A$+")"
40 CLOSE #1
50 CHAIN MERGE "CHAIN.TMP",60,ALL
60 FOR X=0 TO 5
70 REM
80 PRINT X,Y
90 NEXT X
100 GOTO 10

[edit] Harbour

 
Procedure Main()
local bAdd := {|Label,n1,n2| Qout( Label ), QQout( n1 + n2 )}
Eval( bAdd, "5+5 = ", 5, 5 )
Eval( bAdd, "5-5 = ", 5, -5 )
return
 
Upon execution you see:
5+5 = 10
5-5 = 0
 

[edit] HicEst

XEQ invokes the interpreter on a string of HicEst code, but keeps the current dictionary and stack state. Blocks of expressions are not possible.

value = XEQ( " temp = 1 + 2 + 3 ") ! value is assigned 6
! temp is undefined outside XEQ, if it was not defined before.
 
XEQ(" WRITE(Messagebox) 'Hello World !' ")
 
OPEN(FIle="my_file.txt")
READ(FIle="my_file.txt", Row=6) string
XEQ( string ) ! executes row 6 of my_file.txt

[edit] J

Use monadic ". (Do) to execute a string.

". 'a =: +/ 1 2 3' NB. execute a string to sum 1, 2 and 3 and assign to noun a

Only J expressions are allowed in strings used as as arguments for ". (control words and blocks of expressions are not allowed).

Alterntively, you can use the conjunction : (Explicit Definition) to create various kinds of functions and evaluate them. Arguments have names, such as "y", which are specified by the language definition. For example:

monad :'+/y' 1 2 3

Rules of scope for such functions match those described on the Scope modifiers page. Also, control words (like if. or for. or while.) and blocks of expressions are allowed in strings which are evaluated in this fashion.

The context for these evaluations will always be the current locale (which might typically be the current object [or class]). If only expressions are allowed, then local variables will be local to the current explicit definition. Otherwise a new local context will be created for the evaluation (and this will be discarded when evaluation has completed). Local contexts are lexical while locales may also be manipulated programatically.

Debugging facilities [currently] require that the operation be given a name.

J relies on the OS for sandboxing and does not offer any additional resource constraints.


[edit] Lasso

"Sourcefile" when executed has access to all variables and other data that would be available in scope to an included file.

This means thread vars ($) and types/methods already defined will be accessible.

Types, methods, traits and thread vars created or modified will maintain state subsequently - i.e. if a type is defined in code executed in a sourcefile context then that type will be available after execution. if a thread var is modified in the sourcefile executed code then the var will maintain that value after execution.

Local variables (#) maintain scope behaviour as normal.

Output is governed by the "autocollect" boolean, the third parameter in the sourcefile invocation.

//code, fragment name, autocollect, inplaintext
local(mycode = "'Hello world, it is '+date")
sourcefile('['+#mycode+']','arbritraty_name', true, true)->invoke
 
'\r'
 
 
var(x = 100)
local(mycode = "Outside Lasso\r['Hello world, var x is '+var(x)]")
// autocollect (3rd param): return any output generated
// inplaintext (4th param): if true, assumes this is mixed Lasso and plain text,
// requires Lasso code to be in square brackets or other supported code block demarkation.
sourcefile(#mycode,'arbritraty_name', true, true)->invoke
 
'\r'
 
var(y = 2)
local(mycode = "'Hello world, is there output?\r'
var(x) *= var(y)")
// autocollect (3rd param): as false, no output returned
// inplaintext (4th param): as false, assumes this is Lasso code, no mixed-mode Lasso and text.
sourcefile(#mycode,'arbritraty_name', false, false)->invoke
'var x is now: '+$x
 
'\r'
 
var(z = 3)
local(mycode = "var(x) *= var(z)")
sourcefile(#mycode,'arbritraty_name', false, false)->invoke
'var x is now: '+$x
Output:
Hello world, it is 2013-11-10 15:54:19
Outside Lasso
Hello world, var x is 100
var x is now: 200
var x is now: 600

[edit] Liberty BASIC

Liberty BASIC has the ability to evaluate arrays using a string for the array name and a variable for the element.

 
'Dimension a numerical and string array
Dim myArray(5)
Dim myStringArray$(5)
 
'Fill both arrays with the appropriate data
For i = 0 To 5
myArray(i) = i
myStringArray$(i) = "String - " + str$(i)
Next i
 
'Set two variables with the names of each array
numArrayName$ = "myArray"
strArrayName$ = "myStringArray"
 
'Retrieve the array data by evaluating a string
'that correlates to the array
For i = 0 To 5
Print Eval$(numArrayName$ + "(" + str$(i) + ")")
Print Eval$(strArrayName$ + "$(" + str$(i) + ")")
Next i

An example using a struct and a pointer.

 
Struct myStruct, value As long, _
string As ptr
myStruct.value.struct = 10
myStruct.string.struct = "Hello World!"
 
structName$ = "myStruct"
numElement$ = "value"
strElement$ = "string"
 
Print Eval$(structName$ + "." + numElement$ + "." + "struct")
 
'Pay close attention that this is EVAL() because we are
'retrieving the PTR to the string which is essentially a ulong
Print Winstring(Eval(structName$ + "." + strElement$ + "." + "struct"))

[edit] Lua

f = loadstring(s) -- load a string as a function. Returns a function.
 
one = loadstring"return 1" -- one() returns 1
 
two = loadstring"return ..." -- two() returns the arguments passed to it

In Lua 5.2 the loadstring function is superseded by the more general load function, which can be used in a compatible way. Nevertheless, loadstring is still available.

Works with: Lua version 5.2
f = load("return 42")
f() --> returns 42

[edit] JavaScript

The eval method handles statements and expressions well:

 
var foo = eval('{value: 42}');
eval('var bar = "Hello, world!";');
 
typeof foo; // 'object'
typeof bar; // 'string'
 

[edit] MATLAB

The eval and evalin functions handles any kind of code. It can handle multi-line code, although it needs the lines to be separated by the newline character. It can even allow you to program at runtime, as illustrated in the last example in the code and output below. Errors can occur when mixing eval statements with regular code, especially "compile-time" errors if the code appears to be missing key elements (ending brackets or end statements, etc). Some of these are also demonstrated.

function testEval
fprintf('Expressions:\n')
x = eval('5+10^2')
eval('y = (x-100).*[1 2 3]')
eval('z = strcat(''my'', '' string'')')
try
w eval(' = 45')
catch
fprintf('Runtime error: interpretation of w is a function\n\n')
end
% eval('v') = 5
% Invalid at compile-time as MATLAB interprets as using eval as a variable
 
fprintf('Other Statements:\n')
nl = sprintf('\n');
eval(['for k = 1:20' nl ...
'fprintf(''%.3f\n'', k)' nl ...
'if k == 3' nl ...
'break' nl ...
'end' nl ...
'end'])
true == eval('1')
try
true eval(' == 1')
catch
fprintf('Runtime error: interpretation of == 1 is of input to true\n\n')
end
 
fprintf('Programming on the fly:\n')
userIn = true;
codeBlock = '';
while userIn
userIn = input('Enter next line of code: ', 's');
codeBlock = [codeBlock nl userIn];
end
eval(codeBlock)
end
Output:
Expressions:

x =

   105


y =

     5    10    15


z =

my string

Runtime error: interpretation of w is a function

Other Statements:
1.000
2.000
3.000

ans =

     1

Runtime error: interpretation of == 1 is of input to true

Programming on the fly:
Enter next line of code: fprintf('Goodbye, World!\n')
Enter next line of code: str = 'Ice and Fire';
Enter next line of code: words = textscan(str, '%s');
Enter next line of code: fprintf('%s ', words{1}{end:-1:1})
Enter next line of code: 
Goodbye, World!
Fire and Ice

[edit] Maxima

/* Here is how to create a function and return a value at runtime. In the first example,
the function is made global, i.e. it still exists after the statement is run. In the second example, the function
is declared local. The evaluated string may read or write any variable defined before eval_string is run. */
 
kill(f)$
 
eval_string("block(f(x) := x^2 + 1, f(2))");
5
 
fundef(f);
/* f(x) := x^2 + 1 */
 
eval_string("block([f], local(f), f(x) := x^3 + 1, f(2))");
9
 
fundef(f);
/* f(x) := x^2 + 1 */


[edit] ooRexx

The ooRexx INTERPRET instruction allows execution of dynamically constructed code. Almost any well-formed code can be executed dynamically, including multiple instructions at a time. The instructions are executed in the local context where the interpret instruction executes, so full access to the current variable context is available. For example:

 
a = .array~of(1, 2, 3)
ins = "loop num over a; say num; end"
interpret ins
 

Executes the LOOP instruction, displaying the contents of the array pointed to by variable A.

[edit] OxygenBasic

Runtime (secondary) compiling is possible, with some restrictions. For instance static variables may not be created by the compiled code, but parental variables are visible to it. This demo produces tables of Y values, given a formula, and a range of X values to step through.

 
 
function ExecSeries(string s,double b,e,i) as string
'===================================================
'
sys a,p
string v,u,tab,cr,er
'
'PREPARE OUTPUT BUFFER
'
p=1
cr=chr(13) chr(10)
tab=chr(9)
v=nuls 4096
mid v,p,s+cr+cr
p+=4+len s
'
double x,y,z 'shared variables
'
'COMPILE
'
a=compile s
er=error
if er then
print "runtime error: " er : exit function
end if
'
'EXECUTE
'
for x=b to e step i
if p+128>=len v then
v+=nuls len(v) 'extend buffer
end if
call a
u=str(x) tab str(y) cr
mid v,p,u : p+=len u
next
'
freememory a 'release compiled code
'
return left v,p-1 'results
'
end function
 
'=====
'TESTS
'=====
 
'Expression, StartVal, EndVal stepVal, Increment
 
print ExecSeries "y=x*x*x", 1, 10, 1
print ExecSeries "y=sqrt x",1, 9 , 1
 
 

[edit] Oz

declare
%% simplest case: just evaluate expressions without bindings
R1 = {Compiler.virtualStringToValue "{Abs ~42}"}
{Show R1}
 
%% eval expressions with additional bindings and
%% the possibility to kill the evaluation by calling KillProc
KillProc
R2 = {Compiler.evalExpression "{Abs A}" unit('A':~42) ?KillProc}
{Show R2}
 
%% full control: add and remove bindings, eval expressions or
%% statements, set compiler switches etc.
Engine = {New Compiler.engine init}
{Engine enqueue(setSwitch(expression false))} %% statements instead of expr.
{Engine enqueue(mergeEnv(env('A':42 'System':System)))}
{Engine enqueue(feedVirtualString("{System.show A}"))}

By restricting the environment it is possible to restrict what kind of programs can be run.

[edit] PARI/GP

Since GP is usually run from the REPL gp, it is trivial to evaluate programs at runtime (most are run this way). Slightly less trivial is passing code around as a first-class object:

runme(f)={
f()
};
 
runme( ()->print("Hello world!") )

One facility designed for restricting such embedded programs is default(secure,1) which denies scripts the ability to run system and extern. This cannot be turned off except interactively.

[edit] Perl

The eval function accepts a block or a string as its argument. The difference is that a block is parsed at compile-time, whereas a string is parsed at runtime. The block or string may represent any valid Perl program, including a single expression. The subprogram executes in the same lexical and dynamic scope as the surrounding code. The return value of a call to eval depends on how the subprogram terminates:

  • If control reaches the end of the subprogram, eval returns the value of the last expression evaluated.
  • If the subprogram uses an explicit return, eval returns the given value.
  • If the subprogram throws an exception, eval returns undef. The text of the exception is assigned to $@. (When the subprogram terminates without an exception, $@ is set to the null string instead.)
my ($a, $b) = (-5, 7);
$ans = eval 'abs($a * $b)'; # => 35

[edit] Perl 6

Any syntactically valid sequence of statements may be run, and the snippet to be run can see its outer lexical scope at the point of the eval:

my ($a, $b) = (-5, 7);
my $ans = eval 'abs($a * $b)'; # => 35

Unlike in Perl 5, eval in Perl 6 only compiles and executes the string, but does not trap exceptions. You must say try eval to get that behavior (or supply a CATCH block within the text to be evaluated).

[edit] PHP

The eval construct allow string evaluation as PHP code. Opening and closing tags are not required. Return statements immediatly terminates evaluation . Eval returns NULL, unless return is called in evalued code.

 
<?php
$code = 'echo "hello world"';
eval($code);
$code = 'return "hello world"';
print eval($code);
 

[edit] PicoLisp

In PicoLisp there is a formal equivalence of code and data. Almost any peace of data is potentially executable. PicoLisp has three internal data types: Numbers, symbols and lists. Though in certain contexts (e.g. GUI objects) also atomic data (numbers and symbols) are evaluated as code entities, a typical executable item is a list.

The PicoLisp reference distinguishes between two terms: An 'exe' (expression) is an executable list, with a function as the first element, followed by arguments. A 'prg' (program) is a list of 'exe's, to be executed sequentially.

'exe's and 'prg's are implicit in the whole runtime system. For example, the body of a function is a 'prg', the "true" branch of an 'if' call is an 'exe', while the "false" branch again is a 'prg'.

For explicit execution, an 'exe' can be evaluated by passing it to the function 'eval', while a 'prg' can be handled by 'run'.

As PicoLisp uses exclusively dynamic binding, any 'exe' or 'prg' can be executed in arbitrary contexts. The environmet can be controlled in any conceivable way, through implicit function parameter bindings, or explicitly with the aid of functions like 'bind', 'let' or 'job'.

[edit] Pike

Pike provides compile_string() and compile_file() which can compile code into a class that can be instantiated:

program demo = compile_string(#"
string name=\"demo\";
string hello()
{
return(\"hello, i am \"+name);
}"
);
 
demo()->hello();
Result: "hello, i am demo"

an actual application of this is shown in Simple database.

[edit] Python

Works with: Python version 2.x

The exec statement allows the optional passing in of global and local names via mappings (See the link for full syntax). The example below shows exec being used to parse and execute a string containing two statements:

>>> exec '''
x = sum([1,2,3,4])
print x
'''

10
Works with: Python version 3.x

Note that in Python 3.x exec is a function:

>>> exec('''
x = sum([1,2,3,4])
print(x)
'''
)
10

[edit] R

In R, expressions may be manipulated directly as abstract syntax trees, and evaluated within environments.

quote() captures the abstract syntax tree of an expression. parse() does the same starting from a string. call() constructs an evaluable parse tree. Thus all these three are equivalent.

expr1 <- quote(a+b*c)
expr2 <- parse(text="a+b*c")[[1]]
expr3 <- call("+", quote(`a`), call("*", quote(`b`), quote(`c`)))

eval() evaluates a quoted expression. evalq() is a version of eval() which quotes its first argument.

> a <- 1; b <- 2; c <- 3
> eval(expr1)
[1] 7

eval() has an optional second environment which is the lexical environment to evaluate in.

> env <- as.environment(list(a=1, b=3, c=2))
> evalq(a, env)
[1] 1
> eval(expr1, env) #this fails; env has only emptyenv() as a parent so can't find "+"
Error in eval(expr, envir, enclos) : could not find function "+"
> parent.env(env) <- sys.frame()
> eval(expr1, env) # eval in env, enclosed in the current context
[1] 7
> assign("b", 5, env) # assign() can assign into environments
> eval(expr1, env)
[1] 11

[edit] Racket

Racket has the usual eval that is demonstrated here, and in addition, it has a sandbox environment that provides a safe evaluator that is restricted from accessing files, network, etc.

 
#lang racket
(require racket/sandbox)
(define e (make-evaluator 'racket))
(e '(define + *))
(e '(+ 10 20))
(+ 10 20)
;; (e '(delete-file "/etc/passwd"))
;; --> delete-file: `delete' access denied for /etc/passwd
 

And, of course, both of these methods can use Racket's multilingual capabilities and evaluate the code in a language with different semantics.

[edit] REBOL

The do function evaluates a script file or a series of expressions and returns a result.

It performs the fundamental interpretive action of the Rebol language and is used internally within many other functions such as if, case, while, loop, repeat, foreach, and others.

a: -5
b: 7
answer: do [abs a * b] ; => 35

[edit] REXX

This REXX program does a:

  •     run-time evaluation of an internal expression,   and
  •     run-time evaluation of a user-prompted expression.
/*REXX program illustrates ability to execute code entered at "runtime".*/
numeric digits 10000000 /*ten million digits should do it*/
bee=51
stuff= 'bee=min(-2,44); say 13*2 "[from inside the box.]"; abc=abs(bee)'
interpret stuff
say 'bee=' bee
say 'abc=' abc
say
/* [↓] now, we hear from da user*/
say 'enter an expression:'
pull expression
say
say 'expression entered is:' expression
 
interpret '?='expression
 
say
say 'length of result='length(?)
say ' left 50 bytes of result='left(?,50)'···'
say 'right 50 bytes of result=···'right(?,50)
 
/*stick a fork in it, we're done.*/

output with the input of: 2**44497 - 1
which happens to be the 27th Mersenne prime.

26 [from inside the box.]
bee= -2
abc= 2

enter an expression:
2**44497 - 1

expression entered is: 2**44497 - 1

length of result=13395
 left 50 bytes of result=85450982430363380319330070531840303650990159130402···
right 50 bytes of result=···22977396345497637789562340536844867686961011228671

[edit] Ruby

The eval method evaluates a string as code and returns the resulting object. With one argument, it evaluates in the current context:

a, b = 5, -7
ans = eval "(a * b).abs" # => 35

With two arguments, eval runs in the given Binding or Proc context:

def first(main_var, main_binding)
foo = 42
second [[main_var, main_binding], ["foo", binding]]
end
 
def second(args)
sqr = lambda {|x| x**2}
deref(args << ["sqr", binding])
end
 
def deref(stuff)
stuff.each do |varname, context|
puts "value of #{varname} is #{eval varname, context}"
end
end
 
hello = "world"
first "hello", binding
value of hello is world
value of foo is 42
value of sqr is #<Proc:[email protected]:7>

[edit] Scheme

In Scheme, the expression passed to eval is evaluated in the current interaction environment, unless otherwise specified. The result is read back as a Scheme value.

> (define x 37)
> (eval '(+ x 5))
42
> (eval '(+ x 5) (interaction-environment))
42
> (eval '(+ x 5) (scheme-report-environment 5)) ;; provides R5RS definitions
 
Error: identifier not visible x.
Type (debug) to enter the debugger.
> (display (eval (read)))
(+ 4 5) ;; this is input from the user.
9

[edit] Sidef

The eval method evaluates a string as code and returns the resulting object.

var (a, b) = (-5, 7);
say eval '(a * b).abs'; # => 35
say (a * b -> abs); # => 35

[edit] Slate

In Slate, programs are represented as Syntax Node trees, with methods defined on the various syntactic types. The backtick syntax provides a convenient quoting mechanism, and as objects, they have convenient methods defined for evaluation or evaluation within a specific environment:

`(4 + 5) evaluate.
`(4 + 5) evaluateIn: prototypes.

You can also explicitly invoke the Parser on a String, to convert it into syntactic objects:

(Syntax Parser newOn: '4 + 5') upToEnd do: [| :each | print: each evaluate]

You can construct a program using externally-specified values using `unquote within a quoted expression:

define: #x -> 4.
`(x `unquote + 5) evaluate.

Or you can obviously construct a string:

define: #x -> 4.
(Syntax Parser newOn: x printString ; ' + 5')

The evaluate method also takes into consideration the current lexical scope, unless another environment is specified. The following returns 10, no matter what binding x has in the local namespace:

define: #x -> 4.
[| x | x: 5. `(x `unquote + 5) evaluate] do.

Slate can sandbox via constructing a fresh namespace and evaluating within it, but this mechanism is not strongly secure yet.

[edit] Smalltalk

[ 4 + 5 ] value.

Evaluating an expression without bindings:

e := ' 123 degreesToRadians sin '.
Transcript show: (Compiler evaluate: e) .

To get local bindings (x, y), evaluate an expression which yields a block given as a string, then call the resulting block:

e := '[ :x :y | (x*x + (y*y)) sqrt ]'.
Transcript show: ((Compiler evaluate: e) value: 3 value: 4).

this could be wrapped into a utility, which expects the names to bind as argument, if required.

[edit] SNOBOL4

The built in function eval() evaluates SNOBOL4 expressions and returns the value. The expression is evaluated in the current environment and has access to then-current variables.

     expression = "' page ' (i + 1)"
i = 7
output = eval(expression)
end

Output:

 page 8

The built in function code() compiles complete SNOBOL4 source statements, or even complete programs. The compiled program is returned (as a value of type CODE), and when executed the program is executed in the then-current environment and has access to the then-current variables. Labels in the compiled program are added to the current program. Programs of type CODE are executed by a variant of the goto clause:

     compiled = code(' output = "Hello, world."')  :s<compiled>
end

When passing programs to code(), semicolons are used to separate lines.

The calling (already-compiled) program can call, for example, functions that are defined in the code compiled at runtime, and can include gotos to labels only defined in the code compiled at runtime. Likewise, the code compiled at runtime has access to not just variables, but also files, functions, etc., that are in the already-compiled program.

[edit] Sparkling

In Sparkling, the standard library provides functions to compile expressions and statements into functions. Each such function is considered a different top-level program, running in the execution context of it's "parent" program (i. e. the piece of code from within which it was created). Consequently, functions compiled at runtime share their environment (e. g. all globals) with their parent program.

Compiled expressions and statements can take arbitrary arguments and return values to the caller. As with any function, the expression or statement being compiled can refer to its arguments using the # prefix operator.

An expression always "returns" a value (i. e. evaluates to one) to the caller. Basically, compiling an expression is semantically (and syntactically) equivalent with creating a function with no declared arguments of which the body consists of a single return statement, returning the expression.

[edit] Evaluating expressions

[edit] Simple

let fn = exprtofn("13 + 37");
fn() // -> 50

[edit] With arguments

let fn = exprtofn("#0 * #1");
fn(3, 4) // -> 12

[edit] Evaluating statements

let fn = compile("for (var i = 0; i < 10; i++) { print(i); }");
fn(); // result: 0 1 2 3 4 5 6 7 8 9

[edit] Tcl

[edit] Simple Evaluation

Evaluation in the current interpreter:

set four 4
set result1 [eval "expr {$four + 5}"] ;# string input
 
set result2 [eval [list expr [list $four + 5]]] ;# list input

[edit] Evaluation in a restricted context

Tcl handles sandboxing by creating new interpreters. Each interpreter is strongly isolated from all other interpreters except in that the interpreter that creates a sub-interpreter retains management control over that “slave” interpreter. The exact capabilities exposed in the slave are controlled by what commands exist in it; commands in the slave may be aliases for other commands in the master interpreter, which allows for trapping into a more highly authorized context (which can be considered analogous to a system call to an OS kernel).

# Create an interpreter with a default set of restrictions
interp create -safe restrictedContext
 
# Our secret variable
set v "secret"
 
# Allow some guarded access to the secret from the restricted context.
interp alias restrictedContext doubleSecret {} example
proc example {} {
global v
lappend v $v
return [llength $v]
}
 
# Evaluate a script in the restricted context
puts [restrictedContext eval {
append v " has been leaked"
catch {file delete yourCriticalFile.txt} ;# Will be denied!
return "there are [doubleSecret] words in the secret: the magic number is [expr {4 + 5}]"
}]; # --> there are 2 words in the secret: the magic number is 9
puts $v; # --> secret secret

As can be seen, the result of the overall evaluation is the same as the result of the evaluation in the slave.

Note that with providing values to the restricted context, it is normal to do this by providing an alias/trap command in the restricted context to allow the script to pick up the value when it wants it. Although the value could also have been provided by setting a variable in the restricted context, this is fairly unusual in practice. The example above shows how this might be done with the result of the doubleSecret command.

[edit] Evaluation within limits

Works with: Tcl version 8.5

Even stronger protection of the master interpreter is available from Tcl 8.5 onwards through the setting of resource limits on the slaves. These allow the master to prevent the evaluated script from going berserk:

set i [interp create]
interp limit $i commands -value [expr [$i eval info cmdcount]+20] -granularity 1
interp eval $i {
set x 0
while {1} { # Infinite loop! Bwahahahaha!
puts "Counting up... [incr x]"
}
}

This produces the output (the last line is an error message):

Counting up... 1
Counting up... 2
Counting up... 3
Counting up... 4
Counting up... 5
Counting up... 6
Counting up... 7
Counting up... 8
Counting up... 9
Counting up... 10
command count limit exceeded

[edit] TI-89 BASIC

The function expr(string) evaluates the string as an expression. It is evaluated in the environment of the calling program (it can see local variables).

The Exec string, args... statement executes arbitrary 68k machine code (and is thus entirely unsafe).

TODO: Is there a way to execute statements as well as evaluate expressions?

[edit] UNIX Shell

eval is the command to use:

$ a=42
$ b=a
$ eval "echo \$$b"
42

[edit] zkl

In zkl, the compiler is part of the language and compiling a chunk of code returns an executable (which how the REPL works), so
Compiler.Compiler.compileText(
"fcn f(text){text.len()}").f("foobar")
//-->6

All language constructs are allowed, the only sand boxing is the new code can only touch global resources or items explicitly passed in ("foobar" in the example).

Personal tools
Namespaces

Variants
Actions
Community
Explore
Misc
Toolbox