Runtime evaluation: Difference between revisions

Content added Content deleted
No edit summary
(Provide additional information about J)
Line 264: Line 264:


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.
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 [http://wiki.jsoftware.com/help/primer/locale.htm 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.


=={{header|Lua}}==
=={{header|Lua}}==