Scripting environment not fully scriptable

[Martin Sjölund]

Many of the scripting functions are elaborated like this:
{{{ case (cache,env,Absyn.CREF_IDENT(name = "system"),{Absyn.STRING(value = str)},{},impl,SOME(st),_,_)

then (cache, makeBuiltinCall("system",{DAE.SCONST(str)},DAE.ET_INT()),DAE.PROP(DAE.T_INTEGER_DEFAULT,DAE.C_VAR()),SOME(st));}}}

This means they can only take string literals as input. But if the function is really intended to be scriptable, it should be able to take any expression as input.

[Martin Sjölund]

Some parts of this can now be scripted (ExpressionSimplify will be called on the input expressions)

[Martin Sjölund]

Ceval is now called on the arguments of many CevalScript functions (but not all)

[Martin Sjölund]

Also note that Static needs special handlers for CODE input (crefs and stuff) because we have not introduced it to the type system.

[Martin Sjölund]

Most of the CevalScript functionality is now scriptable (the new function Ceval's all input arguments).