On Sat, Oct 18, 2008 at 5:00 AM, klaas.holwerda <[EMAIL PROTECTED]> wrote:
> Hi John,
>
> Started some serious wrapping now, and understand that it is no so
> automatic as i hoped :-)
> Anyway the tag extraction script give a reasonable start. But when it
> come to operator its a bit bad.
> I tried to fix it by adding %operator in front of those members in
> parse_ctags, but that should not be done for all.
> Now i could make it work for the operators that are oke. But what about
> the rest??
>
> So i wonder, where is the real problem, in Lua in C++. Is it possible to
> have operators like below?
> Or should they somehow be renamed? What would be a good solution??
>
> Anyway the next one refuses to compile in C++.
>
> a2dIOHandlerXMLWrite& operator<<(const wxInt16 & c)
>
> It does not like the name of the array variable.
>
> static wxLuaArgType
> s_wxluatypeArray_wxLua_a2dIOHandlerXMLWrite_operator<<[] = {
> &wxluatype_a2dIOHandlerXMLWrite, &wxluatype_TLIGHTUSERDATA, NULL };
I forgot to add the << and >> operators so they are not handled
properly. I'll try to look into it tonight.
-John
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
wxlua-users mailing list
wxlua-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxlua-users
