Re: Fosdem talk on pain of moving from Python 2.x to 3.x

[Viacheslav Usov <via.usov@...>]

On Thu, Feb 8, 2018 at 4:04 PM, Luiz Henrique de Figueiredo <lhf@tecgraf.puc-rio.br> wrote:

> If you embed Lua in C, I suppose you will get symbol conflicts, so you will
> have to modify the source of one of the versions to prefix exported symbols.

I have done this once or twice with success. I can dig up the tools
I've used if there is any interest.

The following suggestion/request has been sitting in my drafts for some time.

A make-time option to include Lua API pointers in the Lua state structure, so that, for example, lua_absindex could be alternatively called as, for example, L->api->absindex(L, -1) and a related make-time option that defines all API functions as macros such that, for for example,  lua_absindex(L, -1) expands into  L->api->absindex(L, -1). The purpose of this is manifold, including (1) a possibility to host Lua as a statically linked library while loading external C-language Lua libraries and (2) eventually a possibility to host multiple versions of Lua.

Is that just a wild fantasy?

Cheers,

V.