wxlua-users — wxLua list for users and developers

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

[Steve K. <ha...@ya...>]

All right, I fixed this but not understand why ; You may have the answer though lol

What I did is; after comapring liles by lines with wxLua.cpp then add  

extern bool wxLuaBinding_wxstc_init();

and init it of course

wxLuaBinding_wxstc_init();

as I saw that is the only main difference between wxlua and my exe file. Result: No longer the f*** message 

wxLua: Memory allocation error  

in any script it runs.

Why I need stc  where I did not use any of them in lua script. And why this error only happen in win98? It is mysterious.

Thank you for your replies now I can sleep well tonight :-)

Cheers,




S.KIEU
 Send instant messages to your online friends http://au.messenger.yahoo.com 

[Wxlua-users] Windows, MinGW, Error

[<ld...@tu...>]

Hi

Sorry for my English, it is not my native language...


Windows2000, MinGW
$ gcc -v
Reading specs from c:/MinGW/bin/../lib/gcc/mingw32/3.4.2/specs
Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-a=
s
--host=3Dmingw32 --target=3Dmingw32 --prefix=3D/mingw --enable-threads
--disable-nls --enable-languages=3Dc,c++,f77,ada,objc,java
--disable-win32-registry --disable-shared --enable-sjlj-exceptions
--enable-libgcj --disable-java-awt --without-x --enable-java-gc=3Dboehm=

--disable-libgcj-debug --enable-interpreter --enable-hash-synchronizati=
on
--enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.2 (mingw-special)

When i try compile latest snapshot wxLua_Snapshot_2006-06-07.tar.gz, I =
get
error.....

.././bk-deps g++ -c -o wxbind_dll_wx_bind.o -I../modules/wxbind/setup
-I../modules -I./.. -DWXMAKINGDLL_WXBIND
-I/usr/local/lib/wx/include/msw-ansi-release-2.6
-I/usr/local/include/wx-2.6 -D__WXMSW__ -mthreads -DWXUSINGDLL=3D1
-DNO_GCC_PRAGMA    -g0 -O2 ../modules/wxbind/src/wx_bind.cpp
../modules/wxbind/src/wx_bind.cpp: In function `int
wxLua_function_wxHandleFatalExceptions(lua_State*)':
../modules/wxbind/src/wx_bind.cpp:4061: error: `wxHandleFatalExceptions=
'
undeclared (first use this function)
../modules/wxbind/src/wx_bind.cpp:4061: error: (Each undeclared identif=
ier
is reported only once for each function it appears in.)
../modules/wxbind/src/wx_bind.cpp:3017: confused by earlier errors, bai=
ling
out
make[1]: *** [wxbind_dll_wx_bind.o] Error 1
make[1]: Leaving directory `/home/Ldn/wxLua/modules'
make: *** [modules] Error 2


Problem is here

modules/wxbind/wx_bind.cpp:4060

static int LUACALL wxLua_function_wxHandleFatalExceptions(lua_State *L)=

{
    wxLuaState wxlState(L);
    bool returns;
    // get number of arguments
    int argCount =3D lua_gettop(L);
    // bool doIt =3D true
    bool doIt =3D (argCount >=3D 1 ? wxlState.GetBooleanType(1) : true)=
;
    // call wxHandleFatalExceptions
    returns =3D wxHandleFatalExceptions(doIt);
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    // push the result flag
    lua_pushboolean(L, returns);

    return 1;
}

If I am remark it

//returns =3D wxHandleFatalExceptions(doIt);

and continue compiling I get error

$ make
(cd ./modules/ && make )
make[1]: Entering directory `/home/Ldn/wxLua/modules'
.././bk-deps g++ -c -o wxbind_dll_wx_bind.o -I../modules/wxbind/setup
-I../modules -I./.. -DWXMAKINGDLL_WXBIND
-I/usr/local/lib/wx/include/msw-ansi-release-2.6
-I/usr/local/include/wx-2.6 -D__WXMSW__ -mthreads -DWXUSINGDLL=3D1
-DNO_GCC_PRAGMA    -g0 -O2 ../modules/wxbind/src/wx_bind.cpp
../modules/wxbind/src/wx_bind.cpp: In function `WXLUAOBJECT*
wxLuaGetObjectList_wx(size_t&)':
../modules/wxbind/src/wx_bind.cpp:3017: internal compiler error:
output_operand: invalid expression as operand
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
make[1]: *** [wxbind_dll_wx_bind.o] Error 1
make[1]: Leaving directory `/home/Ldn/wxLua/modules'
make: *** [modules] Error 2

Problem is here
modules/wxbind/wx_bind.cpp:2941

#if wxLUA_USE_wxPointSizeRect
        { &wxDefaultPosition, 0, "wxDefaultPosition", &s_wxluatag_wxPoi=
nt
},
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        { &wxDefaultSize, 0, "wxDefaultSize", &s_wxluatag_wxSize },
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#endif


Can you help me to compile wxLua under win32 with MinGW?=

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

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

On 6/8/06, Steve Kieu <ha...@ya...> wrote:
> > 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...
>
> Yeah the lua table, created and used in lua. Very strange indeed, it gives
> error even before running it; Lets say:
>
> 1 Load sqlite3 and init stuff
> 2. wx.wxMessageDialod("Check to see if it reaches here")
> 3. local sql_strs={}
> 4. many   table.insert(sql_strs, "sql string here")
> 6. even not do anything with table here, just end script
>
> Run the file, got error, line 2. not reached.

What is the error exactly? The memory allocation something or other?

> If comment out 4  no error. If not load the sqlite3 modules  no error.
>
> of course the solution is easy, just put a text file each line has a sql
> command and iterate io.lines() on it ; it works. But you know it is one
> example of correct usage

Try using wxLuaFreeze and require for the sqlite3 module and your
code. Does this fail?

> Another case that it gives error is the following simple echo server
>
>  local socket=require"socket" local copas=require"copas" local host = host
> or "localhost" local port = port or 8080 if arg then host = arg[1] or host
> port = arg[2] or port end
>  local function handle_server(skt) skt=copas.wrap(skt) table.foreach
> (skt,print) -- If client do not send quit command it will loop forever :-)
> while true do -- local line, err = copas.receive(skt) local line,
> err=skt:receive() print(line, err) if line=="quit" then break end end end
> print("Binding to host '" ..host.. "' and port " ..port.. "...\n")
>  local server = assert(socket.bind(host, port)) local i, p =
> server:getsockname() assert(i, p) print(i, p,"\n") copas.addserver(server,
> handle_server) copas.loop()
> Last night I have removed all custom bindings but in the exe one still have
> two wxLuaState one in main thread, the other is in a another thread to run a
> log.lua to process log that wxLuaEvent sends (I like that way); this time
> the simpler server  works but the script using sqlite3 still failled.

I'm guessing the sqlite3 module has problems then.

> About the picker, I just add a quick code to use it so it is not concrete
> yet at least I think, it does not check conditions wxLuaUseXXX  etc..

Ok, I'll probably wait until I get a new wxWidgets checkout and add
them all then.

-John Labenski

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

[Steve K. <ha...@ya...>]

> 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...


Yeah the lua table, created and used in lua. Very strange indeed, it gives error even before running it; Lets say:

1 Load sqlite3 and init stuff

2. wx.wxMessageDialod("Check to see if it reaches here")

3. local sql_strs={}

4. many   table.insert(sql_strs, "sql string here")

6. even not do anything with table here, just end script

Run the file, got error, line 2. not reached.
If comment out 4  no error. If not load the sqlite3 modules  no error.

of course the solution is easy, just put a text file each line has a sql command and iterate io.lines() on it ; it works. But you know it is one example of correct usage

Another case that it gives error is the following simple echo server 

      
local socket=require"socket" local copas=require"copas"  local host = host or "localhost" local port = port or 8080 if arg then     host = arg[1] or host     port = arg[2] or port end  local function handle_server(skt)     skt=copas.wrap(skt)          table.foreach (skt,print)          -- If client do not send quit command it will loop forever :-)     while true do --        local line, err = copas.receive(skt)  local line, err=skt:receive()         print(line, err)         if line=="quit" then break end      end end  print("Binding to host '" ..host.. "' and port " ..port.. "...\n") local server = assert(socket.bind(host, port)) local i, p   = server:getsockname() assert(i, p) print(i, p,"\n") copas.addserver(server, handle_server) copas.loop()
Last night I have removed all custom bindings but in the exe one still have two wxLuaState one in main thread, the other is in a another thread to run a log.lua to process log that wxLuaEvent sends (I like that way); this time the simpler server  works but the script using sqlite3 still failled. 


About the picker, I just add a quick code to use it so it is not concrete yet at least I think, it does not check conditions wxLuaUseXXX  etc..

I have tested it, it display ; can GetValue()  can DynamicCast when using XRC;  but not tested all other functions, as I am still busy with the win98 errors...; Just simply add 

      
%include "wx/datectrl.h"
%enum 
wxDP_DEFAULT
wxDP_SPIN
wxDP_DROPDOWN
wxDP_SHOWCENTURY
wxDP_ALLOWNONE
%endenum

%class wxDatePickerCtrl, wxControl

%constructor wxDatePickerCtrl(wxWindow *parent,wxWindowID id, const wxDateTime& date = wxDefaultDateTime, const wxPoint& pos = wxDefaultPosition,const wxSize& size = wxDefaultSize,long style = wxDP_DEFAULT | wxDP_SHOWCENTURY,const wxValidator& validator = wxDefaultValidator, const wxString& name = wxDatePickerCtrlNameStr)

bool GetRange(wxDateTime *dt1, wxDateTime *dt2) 
wxDateTime  GetValue()
void SetRange(const wxDateTime& dt1, const wxDateTime& dt2)
void SetValue(const wxDateTime& dt)
wxDateTime  GetValue() 

%endclass
into my custom .i  file is all I have done.

Will go to winXP now and continue to compile without the loging thread and see ....

Cheers







 

S.KIEU
 Send instant messages to your online friends http://au.messenger.yahoo.com 

Re: [Wxlua-users] multi-level C++ namespaces

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

On 6/8/06, Darwin Slattery <dar...@ho...> wrote:
> Thanks for your reply. I think I'm just missing something small here. From
> your suggestions it seems that what I'm trying to do is completely possible
> in the .i file. Just to clarify one point in your last mail, I'm not looking
> to declare a class within another class declaration - I just want to write
> bindings for classes that have been declared in mulit-level namespaces like
> nsa::nsb::nsc.

It was a very small fix, but in a few different places. In order to
make it work you have to use the fully qualified namespace for both
the %class and the constructor.

The output will be nsa_nsb_MyClass which is reasonable enough, right?
It's too much trouble to try to make nested lua "namespaces" like
wx.nsa.nsb.MyClass.

%class %delete %noclassinfo %encapsulate nsa::nsb::MyClass
    nsa::nsb::MyClass()
    %rename nsa_nsb_MyClassFromInt nsa::nsb::MyClass(int x)
     %constructor nsa_nsb_MyClassFromInt(int x)

You use the %rename tag or %constructor tag for alternate
constructors, but you must replace the :: with _.

> Thank you for your offer of looking at the code. I definitely don't want to
> cause any work for you or the team and any suggestions would be appreciated.
> The attached archive has the .i and MyClass header file and I've included a
> main driver file and makefile.

Thanks for the sample, it really helps and saves me a lot of time when
I people give me a nice little sample to work with.

The next snapshot will contain the fixed binding generator.

Regards,
    John Labenski

Re: [Wxlua-users] wxLua and Lua coroutines

[Leandro M. B. <lmb...@gm...>]

On 6/6/06, John Labenski <jla...@gm...> wrote:
> Thanks for the sample. I had inadvertently broken coroutines when I
> made the require code work.
>
> I've added the sample as coroutine.wx.lua and the next snapshot should
> work for you. I'd update the snapshot right now, but sourceforge seems
> to be having some problems with their ssh server,
> "ssh_exchange_identification: Connection closed by remote host"???

Seems to be working again!

Thanks, John

LMB

Re: [Wxlua-users] multi-level C++ namespaces

[Darwin S. <dar...@ho...>]

Hi,

Thanks for your reply. I think I'm just missing something small here. From 
your suggestions it seems that what I'm trying to do is completely possible 
in the .i file. Just to clarify one point in your last mail, I'm not looking 
to declare a class within another class declaration - I just want to write 
bindings for classes that have been declared in mulit-level namespaces like 
nsa::nsb::nsc.

Thank you for your offer of looking at the code. I definitely don't want to 
cause any work for you or the team and any suggestions would be appreciated. 
The attached archive has the .i and MyClass header file and I've included a 
main driver file and makefile.

Thanks for your help,
Darwin Slattery


From: "John Labenski" <jla...@gm...>
To: djs...@us..., wxl...@li...
Subject: Re: [Wxlua-users] multi-level C++ namespaces
Date: Thu, 8 Jun 2006 15:57:15 -0400

On 6/8/06, Darwin Slattery <dar...@ho...> wrote:
>Just to clarify what I'm trying to do first:
>I have a class called MyClass in a namespace called nsa. Its a very simple

You can easily fake using the namespaces by adding this in the in the
rules file.

-- in lua access as nsa.MyClass
hook_lua_namespace = "nsa"
-- in C++ the code is compiled in namespace nsa
hook_cpp_binding_post_includes = "namespace nsa;\n"

>class with 2 member functions SetX and GetX which set and return an int. I
>would eventually like to move this
>class into sub-namespace of nsa called nsb. My main problem is that I don't
>want to move the
>class into the global C++ namepsace. Ideally I would also like to access

Ugh, this is not something I really want to get involved in. You're
talking about a class like this

class MyClass
{
public:
    class MyClass2
    {
       public:
       int GetX(); void SetX(int x);
       int x;
    }

    Stuff for MyClass
}

>this class in lua by
>using nsa.nsb.MyClass but I don't mind using nsa_nsb.MyClass.

I think you will need to use the latter. To allow you to access
nsa.nsb.MyClass would require significant changes to the binding code
generator and how wxLua deals with looking things up in the bindings.
BUT! see below send me the sample code and if it's not too bad I'll do
it.

>I tried adding "#include \"MyClass.h\"; using nsa::MyClass" in the
>hook_cpp_binding option but this
>produced the following errors:
>wxluanstest.cpp:21: error: 'MyClass' is already declared in this scope
>wxluanstest.cpp: In function 'int wxLua_MyClass_constructor(lua_State*)':
>wxluanstest.cpp:40: error: no matching function for call to
>'wxLua_AddToTrackedMemoryList(wxLuaState&, nsa::MyClass*)'
>/usr/local/include/wxlua/include/wxlbind.h:189: note: candidates are: void
>...

I'd really have to be able to see the input and output code to make
any sense of this. It looks like you have a nice little sample class
and the interface file, could you just post the two of those and I can
take a look at it this weekend.

>Using nsa::MyClass instead of just MyClass in the .i file without the
>hook_cpp_binding
>value above produced:
>
>wxluanstest.h:48: error: 'wxObject_nsa' has not been declared
>wxluanstest.h:48: error: expected unqualified-id before ':' token
>wxluanstest.cpp:110: error: 'wxLua_nsa' has not been declared
>wxluanstest.cpp:111: error: 'wxLua_nsa' has not been declared
>make: *** [wxluanstest.o] Error 1

See above, I'd have to see the output, but I'm guessing that the
generator is not expecting :: to be in a classname and so it's just
doing weird things.

-John Labenski

Re: [Wxlua-users] multi-level C++ namespaces

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

On 6/8/06, Darwin Slattery <dar...@ho...> wrote:
> Just to clarify what I'm trying to do first:
> I have a class called MyClass in a namespace called nsa. Its a very simple

You can easily fake using the namespaces by adding this in the in the
rules file.

-- in lua access as nsa.MyClass
hook_lua_namespace = "nsa"
-- in C++ the code is compiled in namespace nsa
hook_cpp_binding_post_includes = "namespace nsa;\n"

> class with 2 member functions SetX and GetX which set and return an int. I
> would eventually like to move this
> class into sub-namespace of nsa called nsb. My main problem is that I don't
> want to move the
> class into the global C++ namepsace. Ideally I would also like to access

Ugh, this is not something I really want to get involved in. You're
talking about a class like this

class MyClass
{
public:
    class MyClass2
    {
       public:
       int GetX(); void SetX(int x);
       int x;
    }

    Stuff for MyClass
}

> this class in lua by
> using nsa.nsb.MyClass but I don't mind using nsa_nsb.MyClass.

I think you will need to use the latter. To allow you to access
nsa.nsb.MyClass would require significant changes to the binding code
generator and how wxLua deals with looking things up in the bindings.
BUT! see below send me the sample code and if it's not too bad I'll do
it.

> I tried adding "#include \"MyClass.h\"; using nsa::MyClass" in the
> hook_cpp_binding option but this
> produced the following errors:
> wxluanstest.cpp:21: error: 'MyClass' is already declared in this scope
> wxluanstest.cpp: In function 'int wxLua_MyClass_constructor(lua_State*)':
> wxluanstest.cpp:40: error: no matching function for call to
> 'wxLua_AddToTrackedMemoryList(wxLuaState&, nsa::MyClass*)'
> /usr/local/include/wxlua/include/wxlbind.h:189: note: candidates are: void
> ...

I'd really have to be able to see the input and output code to make
any sense of this. It looks like you have a nice little sample class
and the interface file, could you just post the two of those and I can
take a look at it this weekend.

> Using nsa::MyClass instead of just MyClass in the .i file without the
> hook_cpp_binding
> value above produced:
>
> wxluanstest.h:48: error: 'wxObject_nsa' has not been declared
> wxluanstest.h:48: error: expected unqualified-id before ':' token
> wxluanstest.cpp:110: error: 'wxLua_nsa' has not been declared
> wxluanstest.cpp:111: error: 'wxLua_nsa' has not been declared
> make: *** [wxluanstest.o] Error 1

See above, I'd have to see the output, but I'm guessing that the
generator is not expecting :: to be in a classname and so it's just
doing weird things.

-John Labenski

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.

Re: [Wxlua-users] still bindings problems

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

On 6/8/06, klaas.holwerda <kla...@nl...> wrote:
> Hi John,
>
> John Labenski wrote:
> > On 6/7/06, klaas.holwerda <kla...@nl...> wrote:
> >
> >> Your idea to add precompiled headers like this does not work. Also
> >> othere changed you said you made, made no difference.
> >>
> >> hook_cpp_binding_header_includes = "#include
> >> \"general/include/a2dprec.h\"\n..#include \"wxbind/include/wxbind.h\"\n"
> >>
> >> I think the only thing that will be correct is to place the next at as
> >> the first include file in *.cpp generated.
> >> This is what the comment says, and how it worked before.
> >>
> >
> > As I said, just reverting the change will break compilation on X
> > Windows systems since the X windows headers very selfishly #define
> > "Above" and "Below" to be numbers and you have to #undef them *after*
> > including them.
> >
> After some searching i found those in wx_rules.lua. I first had no idea
> what you were talking about :-)
> But indeed how did the come up to use such defines??
> Should they also be placed in say wxluacan_rules.lua, in order to make
> it work on Linux?
> Sofar i did not see a problem on Linux RedHat, but on Suse there are. So
> maybe this is what is the reason.
> Lost my Suse install, so can't check it for the moment.

You only need them if you have a function or something called
Above(...) or Below(...). wxWidgets #undefs them in wx/layout.h since
the layout constraints class has those functions. I've actually made
the bindings #ifdef the layout constraints for < wxchkver26 since
sizers have been around since 2.2 IIRC.

So, no we don't need to add them elsewhere unless there is a
compliation problem.

-John

Re: [Wxlua-users] multi-level C++ namespaces

[Darwin S. <dar...@ho...>]

Thanks for your reply,

I have tried your suggestions but have had no luck unfortunately. I have 
attached
some of the compiler output below.

Just to clarify what I'm trying to do first:
I have a class called MyClass in a namespace called nsa. Its a very simple 
class with 2 member functions SetX and GetX which set and return an int. I 
would eventually like to move this
class into sub-namespace of nsa called nsb. My main problem is that I don't 
want to move the
class into the global C++ namepsace. Ideally I would also like to access 
this class in lua by
using nsa.nsb.MyClass but I don't mind using nsa_nsb.MyClass.

I tried adding "#include \"MyClass.h\"; using nsa::MyClass" in the 
hook_cpp_binding option but this
produced the following errors:
wxluanstest.cpp:21: error: ‘MyClass’ is already declared in this scope
wxluanstest.cpp: In function ‘int wxLua_MyClass_constructor(lua_State*)’:
wxluanstest.cpp:40: error: no matching function for call to 
‘wxLua_AddToTrackedMemoryList(wxLuaState&, nsa::MyClass*)’
/usr/local/include/wxlua/include/wxlbind.h:189: note: candidates are: void 
wxLua_AddToTrackedMemoryList(wxLuaState&, wxObject*)
/usr/local/include/wxbind/include/wxbind.h:2920: note:                 void 
wxLua_AddToTrackedMemoryList(wxLuaState&, wxString*)
/usr/local/include/wxbind/include/wxbind.h:2921: note:                 void 
wxLua_AddToTrackedMemoryList(wxLuaState&, wxWindowDisabler*)
/usr/local/include/wxbind/include/wxbind.h:2929: note:                 void
...



Using nsa::MyClass instead of just MyClass in the .i file without the 
hook_cpp_binding
value above produced:

wxluanstest.h:48: error: ‘wxObject_nsa’ has not been declared
wxluanstest.h:48: error: expected unqualified-id before ‘:’ token
wxluanstest.cpp:110: error: ‘wxLua_nsa’ has not been declared
wxluanstest.cpp:111: error: ‘wxLua_nsa’ has not been declared
make: *** [wxluanstest.o] Error 1


Sorry for the long mail and if you want to look at my code or need any more 
information please
let me know.

Any help would be appreciated,
Darwin Slattery


>I have been having problems with generating the bindings for classes when
>they exist in sub-namespaces of the main namespaces e.g.
>a::b::MyClass
>
>I was not able to set this namesace in the rules file using the
>hook_cpp_namespace because this caused problems with the #ifndef at the top
>of the generated binding header e.g.:
>
><code>
>#ifndef __HOOK_WXLUA_a::b_H__
>#define __HOOK_WXLUA_a::b_H__
></code>

This is ok, hook_cpp_namespace is not really a C++ "namespace", but
rather a way to make sure that the names of the functions and
everything else created by the binding generator are unique.

Try just hook_cpp_namespace = "a_b"

To use a real C++ namespace use one of the
hook_cpp_binding_[XXX_includes] to add any code you need to the
bindings.

>It also seems to only process the first part of the namespace:
>'wxluatest.h:58: error: 'wxObject_a' has not been declared'
>
>I was just wondering if this is supported or if there is any way around 
>this
>short of editing the generated binding files?

Let us know if the above works for you. I do not believe that I've
ever tried using classes within classes so there may be other issues
as well, but lets hope not.

Regards,
    John Labenski

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

[Steve K. <ha...@ya...>]

 
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.  

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

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

cheers



S.KIEU
 Send instant messages to your online friends http://au.messenger.yahoo.com 

Re: [Wxlua-users] wxLua and Lua coroutines

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

Thanks for the sample. I had inadvertently broken coroutines when I
made the require code work.

I've added the sample as coroutine.wx.lua and the next snapshot should
work for you. I'd update the snapshot right now, but sourceforge seems
to be having some problems with their ssh server,
"ssh_exchange_identification: Connection closed by remote host"???

Thanks,
    John Labenski

ps. You can use the wxLuaFreeze program to run wxLua programs from the
command line if you don't want to bother with the c++ side. The wxLua
app can also do it.
$wxlua[freeze] mywxluaprogram.lua


On 6/4/06, Leandro Motta Barros <lmb...@gm...> wrote:
> On 6/4/06, Leandro Motta Barros <lmb...@gm...> wrote:
> > Hello again!
> >
> > On 5/29/06, John Labenski <jla...@gm...> wrote:
> > > [...]
> > > Try unremming the wxPrintf statement in wxLuaState_newthread_handler
> > > in modules/wxlua/src/wxlstate.cpp and see if that gets run when the
> > > coroutine is created. We had to make changes for running wxLua as a
> > > lua module for require, maybe it's broken now.
> >
> > I did it, and 'wxLuaState_newthread_handler()' *is* being called.
> >
> > > [...]
> >
> > > ps. could you send a little coroutine code to show the problem, we
> > > could add it as a sample in wxLua to help verify that they still work.
> > > I seem to have lost my little sample.
> >
> > Here it is: http://www.stackedboxes.org/~lmb/Balaio/wxLuaIdleCoroutine.zip
> >
> > Now, running this example I found some information that may help
> > finding what's going wrong. Here are some notes about this:
> >
> > 1. This example works with the wxLua version I was using before
> > starting to have problems (CVS 2006-04-14). (Just need to change
> > 'Connect' to 'ConnectEvent', and make it look for the 'wxluasetup.h'
> > in the (im)proper place).
> >
> > 2. All other tests made with wxLua Snapshot 2006-06-03.
> >
> > 3. Running the example as is, I get the following output in the console:
> >
> > wxLuaState_newthread_handler L 135088648 L1 135631296, L_wxlsdata
> > 135086608 L1_wxlsdata 135567808
> > lua: Error while running chunk
> > app.lua:41: attempt to call method 'Connect' (a userdata value)
> > stack traceback:
> >         app.lua:41: in function 'new'
> >         app.lua:91: in function <app.lua:80>
> >
> > (notice that 'wxLuaState_newthread_handler()' is called)
> >
> > 4. So, the error happens in the "main thread", not inside the
> > coroutine. This means that the problem is not where I thought it
> > was... (before this, in my application, I was getting the same error,
> > but it was happening (coincidentally?) from inside the coroutine
> > code).
> >
> > 5. I tried to comment out the code that creates the coroutine (and the
> > asserts I added to check if a coroutine is passed to the
> > 'ProgressWindow') and run the program again, just to see where the
> > error would happen. The call to 'Connect' succeeded
>
> Sorry... "send" looks so much like "save" :-)  I still have a final comment...
>
> 6. So, I guess that when the coroutine is created, something is done
> that confuses further calls to wxLua. I haven't checked the wxLua
> implementation, but from these tests, I think my conclusion makes some
> sense.
>
> That's it for now. Feel free to ask for further tests. As I said, I'll
> be busy for some more time, but I can do something whenever I find
> some space in my schedule ;-)
>
> Thanks for all,
>
> LMB
>
>
> _______________________________________________
> Wxlua-users mailing list
> Wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Re: [Wxlua-users] still bindings problems

[klaas.holwerda <kla...@nl...>]

Hi John,

John Labenski wrote:
> On 6/7/06, klaas.holwerda <kla...@nl...> wrote:
>   
>> Your idea to add precompiled headers like this does not work. Also
>> othere changed you said you made, made no difference.
>>
>> hook_cpp_binding_header_includes = "#include
>> \"general/include/a2dprec.h\"\n..#include \"wxbind/include/wxbind.h\"\n"
>>
>> I think the only thing that will be correct is to place the next at as
>> the first include file in *.cpp generated.
>> This is what the comment says, and how it worked before.
>>     
>
> As I said, just reverting the change will break compilation on X
> Windows systems since the X windows headers very selfishly #define
> "Above" and "Below" to be numbers and you have to #undef them *after*
> including them.
>   
After some searching i found those in wx_rules.lua. I first had no idea 
what you were talking about :-)
But indeed how did the come up to use such defines??
Should they also be placed in say wxluacan_rules.lua, in order to make 
it work on Linux?
Sofar i did not see a problem on Linux RedHat, but on Suse there are. So 
maybe this is what is the reason.
Lost my Suse install, so can't check it for the moment.

I understand the split,  there is now hook_cpp_binding_post_includes 
where you put those in.
> I've changed it so that there are now two ways to add code to the cpp
> files. Try using "hook_cpp_binding_includes" again as it is the first
> thing after wx/wxprec.h.
>   
Works fine now, thanks a lot!

Klaas



-- 
Unclassified

[Wxlua-users] Press Update

[Dick C. <xs...@ki...>]

WINNER**WINNER**WINNER**WINNER**WINNER

To All Investors.

Put HRRP on your Radar Screens immediately
Now is the time to do your research. 5:1 Forward Split 
The forward stock split will be effective on or about June 15, 2006, at which 
time the additional shares in certificate form will be mailed directly to 
shareholders without action on their part.

Date: Thursday, June 8, 2006
HE-5 Resources, Corp. 
Symbol: HRRP
Price: $0.47
Position: Positive Buy
Gold, Silver, Copper, Zinc and Platinum

Breaking News was Released
HE-5 Resources, Corp. Extends Record Date of Forward Split 

For pennies you can participate in a ST0CK that could yield results over 
and over again just based on the trading patterns if the company is 
able to effectuate it's business model. 

WATCH OUT!!! 
We could see a GREAT STORY IN THE MAKING. 

GOOD LUCK AND TRADE OUT AT THE TOP!!!!

Sincerely,
Jose Mckinley
RVG Group

Re: [Wxlua-users] multi-level C++ namespaces

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

On 6/7/06, Darwin Slattery <dar...@ho...> wrote:
> I have been having problems with generating the bindings for classes when
> they exist in sub-namespaces of the main namespaces e.g.
> a::b::MyClass
>
> I was not able to set this namesace in the rules file using the
> hook_cpp_namespace because this caused problems with the #ifndef at the top
> of the generated binding header e.g.:
>
> <code>
> #ifndef __HOOK_WXLUA_a::b_H__
> #define __HOOK_WXLUA_a::b_H__
> </code>

This is ok, hook_cpp_namespace is not really a C++ "namespace", but
rather a way to make sure that the names of the functions and
everything else created by the binding generator are unique.

Try just hook_cpp_namespace = "a_b"

To use a real C++ namespace use one of the
hook_cpp_binding_[XXX_includes] to add any code you need to the
bindings.

> It also seems to only process the first part of the namespace:
> 'wxluatest.h:58: error: 'wxObject_a' has not been declared'
>
> I was just wondering if this is supported or if there is any way around this
> short of editing the generated binding files?

Let us know if the above works for you. I do not believe that I've
ever tried using classes within classes so there may be other issues
as well, but lets hope not.

Regards,
    John Labenski

Re: [Wxlua-users] wxLua and Lua coroutines

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

resending since I got a rejection message from SF saying they're
blocking gmail accounts....

On 6/6/06, John Labenski <jla...@gm...> wrote:
> Thanks for the sample. I had inadvertently broken coroutines when I
> made the require code work.
>
> I've added the sample as coroutine.wx.lua and the next snapshot should
> work for you. I'd update the snapshot right now, but sourceforge seems
> to be having some problems with their ssh server,
> "ssh_exchange_identification: Connection closed by remote host"???
>
> Thanks,
>     John Labenski
>
> ps. You can use the wxLuaFreeze program to run wxLua programs from the
> command line if you don't want to bother with the c++ side. The wxLua
> app can also do it.
> $wxlua[freeze] mywxluaprogram.lua
>
>
> On 6/4/06, Leandro Motta Barros <lmb...@gm...> wrote:
> > On 6/4/06, Leandro Motta Barros <lmb...@gm...> wrote:
> > > Hello again!
> > >
> > > On 5/29/06, John Labenski <jla...@gm...> wrote:
> > > > [...]
> > > > Try unremming the wxPrintf statement in wxLuaState_newthread_handler
> > > > in modules/wxlua/src/wxlstate.cpp and see if that gets run when the
> > > > coroutine is created. We had to make changes for running wxLua as a
> > > > lua module for require, maybe it's broken now.
> > >
> > > I did it, and 'wxLuaState_newthread_handler()' *is* being called.
> > >
> > > > [...]
> > >
> > > > ps. could you send a little coroutine code to show the problem, we
> > > > could add it as a sample in wxLua to help verify that they still work.
> > > > I seem to have lost my little sample.
> > >
> > > Here it is: http://www.stackedboxes.org/~lmb/Balaio/wxLuaIdleCoroutine.zip
> > >
> > > Now, running this example I found some information that may help
> > > finding what's going wrong. Here are some notes about this:
> > >
> > > 1. This example works with the wxLua version I was using before
> > > starting to have problems (CVS 2006-04-14). (Just need to change
> > > 'Connect' to 'ConnectEvent', and make it look for the 'wxluasetup.h'
> > > in the (im)proper place).
> > >
> > > 2. All other tests made with wxLua Snapshot 2006-06-03.
> > >
> > > 3. Running the example as is, I get the following output in the console:
> > >
> > > wxLuaState_newthread_handler L 135088648 L1 135631296, L_wxlsdata
> > > 135086608 L1_wxlsdata 135567808
> > > lua: Error while running chunk
> > > app.lua:41: attempt to call method 'Connect' (a userdata value)
> > > stack traceback:
> > >         app.lua:41: in function 'new'
> > >         app.lua:91: in function <app.lua:80>
> > >
> > > (notice that 'wxLuaState_newthread_handler()' is called)
> > >
> > > 4. So, the error happens in the "main thread", not inside the
> > > coroutine. This means that the problem is not where I thought it
> > > was... (before this, in my application, I was getting the same error,
> > > but it was happening (coincidentally?) from inside the coroutine
> > > code).
> > >
> > > 5. I tried to comment out the code that creates the coroutine (and the
> > > asserts I added to check if a coroutine is passed to the
> > > 'ProgressWindow') and run the program again, just to see where the
> > > error would happen. The call to 'Connect' succeeded
> >
> > Sorry... "send" looks so much like "save" :-)  I still have a final comment...
> >
> > 6. So, I guess that when the coroutine is created, something is done
> > that confuses further calls to wxLua. I haven't checked the wxLua
> > implementation, but from these tests, I think my conclusion makes some
> > sense.
> >
> > That's it for now. Feel free to ask for further tests. As I said, I'll
> > be busy for some more time, but I can do something whenever I find
> > some space in my schedule ;-)
> >
> > Thanks for all,
> >
> > LMB
> >
> >
> > _______________________________________________
> > Wxlua-users mailing list
> > Wxl...@li...
> > https://lists.sourceforge.net/lists/listinfo/wxlua-users
> >
>

Re: [Wxlua-users] still bindings problems

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

On 6/7/06, klaas.holwerda <kla...@nl...> wrote:
> Your idea to add precompiled headers like this does not work. Also
> othere changed you said you made, made no difference.
>
> hook_cpp_binding_header_includes = "#include
> \"general/include/a2dprec.h\"\n..#include \"wxbind/include/wxbind.h\"\n"
>
> I think the only thing that will be correct is to place the next at as
> the first include file in *.cpp generated.
> This is what the comment says, and how it worked before.

As I said, just reverting the change will break compilation on X
Windows systems since the X windows headers very selfishly #define
"Above" and "Below" to be numbers and you have to #undef them *after*
including them.

I've changed it so that there are now two ways to add code to the cpp
files. Try using "hook_cpp_binding_includes" again as it is the first
thing after wx/wxprec.h.

hook_cpp_binding_includes
hook_cpp_binding_post_includes

Regards,
    John Labenski

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

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

Ok, thanks for the info. The compilation and linking problems are very
tough to sort out. I remember a long time ago when wxWidgets changed
their compilation flags, a program of mine would crash with absolutely
no backtrace and nothing seemed wrong at all. It was just lucky that I
thought of the flags and after comparing all the different ones for
the libraries I was using and making them the same did things work
normally again.

Good luck,
    John Labenski



On 6/7/06, Steve Kieu <ha...@ya...> wrote:
>
> Okay It might be a compiled problem with sqlite3 module; in the script if I
> comment out the line to load it, it runs. But in another script, it load
> sqlite3 just fine.
>
> so for now I assume it is that library problem. Or sqlite3 problem in win98.
>
>
> Cheers
>
>
> S.KIEU
>
>  Send instant messages to your online friends http://au.messenger.yahoo.com
>
>
> _______________________________________________
> Wxlua-users mailing list
> Wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
>

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

[Steve K. <ha...@ya...>]

Okay It might be a compiled problem with sqlite3 module; in the script if I comment out the line to load it, it runs. But in another script, it load sqlite3 just fine.

so for now I assume it is that library problem. Or sqlite3 problem in win98.

Cheers


S.KIEU
 Send instant messages to your online friends http://au.messenger.yahoo.com 

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

[Steve K. <ha...@ya...>]

I think there is something wrong with compilers (VC7) in this case. I have recompiled wxlua; and now wxlua is ok. But my program still refuses to work. What the strange thing is, yestaerday I add wxDatePickerCtrl bind to my wxLua (in my application name space, so nothing related to wxLua origin) and my app stop working even in GUI script; but still work in another GUI script, so the rule is non GUI script gives error is not correct anymore. The error message is the same: memory allocation error.

The difference between my app and wxLua is I add another lua namespace  and bind some widgets , custom class to lua in that namespace. Again, everything works stable and flawlessly in w2k above . Compiled under winXP using VC7 (Visual Studio .NET 2003) ; optimization /O2 ; blended. wxWidgets Unicode built; and in w98 using unicows.lib link (could it be the problem? to answer this I probably have to recompile the whole tools without unicode support which is ..... )

yes the strange thing is now wxLua works as normal after recompile it. 

I will have to get bottom of this but it may take a while. ANy idea of best way to debug this will be very helpful.


Cheers

S.KIEU
 Send instant messages to your online friends http://au.messenger.yahoo.com 

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

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

resending since I got a rejection message from SF saying they're
blocking gmail accounts....

On 6/5/06, John Labenski <jla...@gm...> wrote:
> On 6/4/06, Steve Kieu <ha...@ya...> wrote:
> > I have repeatedly got the message when running the app in win98. With window
> > 2000 and above, no problem. The app is like:
> >
> > at  wxWidget app, at OnInit I start a wxLuaState and call run a file which
> > is an command line argument.
> > I have a wxThread class in c++ which just very simple thread to spawn
> > another wxLuaState and run a file.lua . This class is accessible in lua
> > script.
> >
> > Basically the first arg is the main window to open the GUI, and there is a
> > menu to allow the thread to run another lua file in a different thread ; a
> > server process. Everything works as expected in win2k . XP, but not win98.
> > Even I do not have thread at all; just use wxLua and run the server script,
> > which is a non GUI apps it gives the memory allocation error as well.
> > However if I use the lua50.exe interprepter it works just fine so at the
> > moment I have to wrap it using os.execute()  call and use lua50.exe.
> >
> > Is there any GUI conflict if we use wxLua to run a Non GUI script in win98?
>
> Not that I know of. It sounds like you know that you cannot call GUI
> functions from a thread, so if you're not doing any GUI stuff in the
> thread wxLuaState there shouldn't be a problem.
>
> Can you debug this? It would be nice to fix, but I regularly use
> multiple wxLuaStates without any problems. I just ran valgrind in
> Linux and I get the usual X windows and GDK errors, which is a shame,
> but nothing from wxLua.
>
> Perhaps you could just make this simple test and see if it works?
>
> wxApp::OnInit()
> {
>    wxLuaState l1(true);
>    wxLuaState l2(true);
>
> Regards,
>     John Labenski
>

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

[Steve K. <ha...@ya...>]

Not that I know of. It sounds like you know that you cannot call GUI
functions from a thread, so if you're not doing any GUI stuff in the
thread wxLuaState there shouldn't be a problem.

Yes, the server process is non gui stuff. Even when there is only one thread, that is I ran the server process alone or any non GUI script, with wxlua.exe it failled. very simple thing like print""  or io.write("smt")
But runs lua50.exe (download from luabinaries) is fine, of course now I can not run wxLua code :-)


wxApp::OnInit()
{
   wxLuaState l1(true);
   wxLuaState l2(true);

I will and let you know later. One thing might be the problem, the win98 I tested is running from vmware ; any chances that vmmon (the memory allocation modules of vmware) is buggy? Unfortunately I do not have a phisical win98 box to test furthur.

The winXP and 2k I tested are real ones though.
catch u later,....



S.KIEU
 Send instant messages to your online friends http://au.messenger.yahoo.com 

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

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

On 6/4/06, Steve Kieu <ha...@ya...> wrote:
> I have repeatedly got the message when running the app in win98. With window
> 2000 and above, no problem. The app is like:
>
> at  wxWidget app, at OnInit I start a wxLuaState and call run a file which
> is an command line argument.
> I have a wxThread class in c++ which just very simple thread to spawn
> another wxLuaState and run a file.lua . This class is accessible in lua
> script.
>
> Basically the first arg is the main window to open the GUI, and there is a
> menu to allow the thread to run another lua file in a different thread ; a
> server process. Everything works as expected in win2k . XP, but not win98.
> Even I do not have thread at all; just use wxLua and run the server script,
> which is a non GUI apps it gives the memory allocation error as well.
> However if I use the lua50.exe interprepter it works just fine so at the
> moment I have to wrap it using os.execute()  call and use lua50.exe.
>
> Is there any GUI conflict if we use wxLua to run a Non GUI script in win98?

Not that I know of. It sounds like you know that you cannot call GUI
functions from a thread, so if you're not doing any GUI stuff in the
thread wxLuaState there shouldn't be a problem.

Can you debug this? It would be nice to fix, but I regularly use
multiple wxLuaStates without any problems. I just ran valgrind in
Linux and I get the usual X windows and GDK errors, which is a shame,
but nothing from wxLua.

Perhaps you could just make this simple test and see if it works?

wxApp::OnInit()
{
   wxLuaState l1(true);
   wxLuaState l2(true);

Regards,
    John Labenski

Re: [Wxlua-users] lua.exe OR lua5.1.exe

[Francesco M. <f18...@ya...>]

klaas.holwerda ha scritto:
> Hi,
> 
> At home i use Vc2003.net and here VC6.
> It seems that VC6 produces wxlua-lua.exe and lua5.1.exe in the wxLua/bin.
> But i am sure i did not see this at home, there i get lua.exe, and not 
> wxlua-lua.exe nor lua5.1.exe.
> 
> I can only explain this because of using VC6 or Vc2003.net.
Did you removed all *.sln and *.vcproj stuff owned by vc2003 and 
reconverted the DSW recently ?
If MSVC6 projects are okay, regenerating SLN and VCPROJ will probably 
solve all problems.


> In any case, what should the real naming be?
> I would prefer the same name on unix and windows.
they are the same on unix and windows.

wxlua-lua is the Lua interpreter built with John's coroutines fixes
lua5.1 is the verbatim lua interpreter identic to those distributes by 
e.g. the LuaBinary project. The name has been chosen to be coherent with 
that project (which as far as I understand provides the official 
binaries of lua).


> Once that is clear we should update the binding generation scripts to 
> use it.
> Although it looks like wxLua/bindings/genwxbind.bat is already using 
> wxlua-lua.exe, but on genwxbind.sh it is lua via the path.
> Why not wxlua-lua.exe also on Unix?
that's just a bug - fixed ;)

Francesco