Re: Getting the callers environment in c

[Chris Gagnon <cgagnon@...>]

On Wed, Mar 9, 2011 at 2:09 PM, Patrick Donnelly <batrick@batbytes.com> wrote:

On Tue, Mar 8, 2011 at 9:02 PM, Chris Gagnon <cgagnon@zindagigames.com> wrote:
> There are many environment tables (a sandbox for each script, which may have
> many functions) and one globally registered utility function in c.
> In the globally registered utility function i need the environment to get at
> the ID.
> I don't have any data to look up the environment with.

Looking up the environment of the caller is not really the hack you
think it is. It's a perfectly legitimate solution.

If you insist on not using it though, you can try to associate the
environment with the thread of the sandbox (each sandbox is in its own
coroutine). This would look nicer because to look up the ID would
simply require doing:

lua_getglobal(L, "ID"); /* looks up in the thread environment table */

--
- Patrick Donnelly

Actually the coroutine method is how i had it working previously.

I'm working to remove the reliance on coroutines to improve performance and memory usage.

Since as it is now all my entry points need to be coroutines for these utility functions to work, 

however only a fraction of them need the ability to suspend / resume.

- Chris