and is still a bad reason :) are you going to use a dynamic language (lua), to script a dynamic language (pharo)?
if you launch a lua interpreter to run a script, you are in practice doing exactly the same as launching a new image to run your script. So you are doing exactly the same as Igor suggested, but replacing one dynamic language with another. and of course, you are "buying" the extra problem of: 1) interact with another language and define the input and output and conversions between one and the other. 2) downgrade the power of pharo into a language who is more limitated. IMO, that's non-sense. Esteban On Dec 12, 2012, at 4:35 PM, Marten Feldtmann <[email protected]> wrote: > And this is the biggest reason to use Lua as a scripting language. > > Marten > > On 12.12.2012 10:47, Igor Stasenko wrote: > >> i think the easiest solution is to run a separate image. >> if you want to run in same image, then you have to modify >> compiler/environment >> for sandboxed code, where nothing can sneak through and access private data. >> >> > <marten.vcf>
