Re: [Wxlua-users] wxLua win98 memory allocation error..

[John L. <jla...@gm...>]

On 6/8/06, Steve Kieu <ha...@ya...> wrote:
>
> Thanks, just a sound - silly question :-) , If I add my custom binding to
> wxLua (in my application code, basically I have my own .i files, and
> genwxlua.sh etc..to generate my own set of bindings in different lua
> namespace, such as cl.   similar like wx.  ) does it in anyway to change the
> way that wxLua allocate memory? It seems that the heap for wxLua runs out in
> win98, even phisical memory is still available.

Not really. The wxLuaState just iterates through the binding list that
was created by calling the wxLuaBinding_XXX_init() functions and runs
the binding class function to push them into the lua_State. Very
little, if any, memory is used for this binding process as all the C++
structures are already created in the wxLuaState so only new
structures in the lua_State are allocated using the lua C API.

> Still the combination:  my exe ; a sqlite3 module loaded, and a relatively
> big table with strings or similar will gives  wxLua Memory allocation error.

Hummm, you mean a lua table created and used in lua? No ideas...

> But use the origin wxlua.exe, things are fine. Iwill try to remove the
> custom binding now to see if it helps.

Yeah, that would be a good idea. The apps/wxlua program uses 3
bindings, wxwidgets, wxstc, and the wxluasocket bindings so if there
was a problem with multiple bindings that program should show it too.

Regards,
    John Labenski

ps. Do you have the complete bindings to the picker controls? If so,
could you post them and I'll add them. In fact if anything else is
missing from wxWidgets itself we'd just assume add it rather than make
you write your own.