Re: C function replacing global environment - why is callingscopeunaffected?

["Bruce Dodson" <bruce_dodson@...>]

Anyway, it wasn't necessarily for loadstring that I wanted
to know.  I just used that in my example because it didn't
require additional code to show it.  Besides, even if the
behavior bothers me (violates the "no surprises if you can
help it" rule), it would be worse for my Lua to handle this
differently than the standard Lua.

"Wim Couwenberg" <wcou@oce.nl> wrote in message
news:001a01c451e1$554986f0$b2a3bc86@oce.nl...
> > If it bothers you though, it's easy enough to redefine
loadstring to
> > use the caller environment.
>