Changes between Version 22 and Version 23 of XL

Show
Ignore:
Author:
dragisha (IP: 89.111.228.7)
Timestamp:
08/22/2009 11:09:52 PM (1 year ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • XL

    v22 v23  
    165165Ideally, ''eval'' is kind of expression, acceptable as XLExprCall in place of statement. [ticket:44 In fact], it's implemented as a builtin procedure in MAIN - visible without qualification. It's also exempted from standard scope handling, and it's context is current one, where it appears, not MAIN as it's usual and normal for all other builtin procedures. 
    166166 
    167 eval("@filename") would be logical form for "evaluating" (dynamically importing module contained in that file, in fact) code from external text file. It would parse, setup, and execute main body. After that, it can be used by subsequent eval's. It would return some kind of handle, but more about it later. __''It's similar to builtin compile(), run(), exec() suite, but not quite - it's external to current interpreters runtime/scopes''__ 
     167eval("@filename") would be logical form for "evaluating" (dynamically importing module contained in that file, in fact) code from external source file. It would parse, setup, and execute main body. After that, it can be used by subsequent eval's. It would return some kind of handle, but more about it later. __''It's similar to builtin compile(), run(), exec() suite, but not quite - it's external to current interpreters runtime/scopes''__ 
    168168 
    169169Also logical would be possibility to destroy dynamically imported modules. With this possibility one can have, for example, XL hosting environment manageable from XL.