wxlua-users — wxLua list for users and developers

Re: [wxlua-users] wxlua upgrade and outstanding issues

[Laurent R. <lr...@iv...>]

Hi Paul,

I'm interested to moving to wxwidgets310 or higher because of support for vc14. I try to use your fork, but I'm not able to compile some projects because of lack of compatibility with old wxWidget classes like wxProperty. 

I tryed to set to 1 the define WXWIN_COMPATIBILITY_2_8 which is set to 0 since wxWidget 3.1.0 but I have encountered lot of others problems. Have you override some others define to be able to compile ? Did I miss something ?

Laurent.


-----Message d'origine-----
De : Paul K [mailto:pau...@ya...] 
Envoyé : samedi 5 mars 2016 23:27
À : wxl...@li...
Objet : Re: [wxlua-users] wxlua upgrade and outstanding issues

Hi All,

> manual changes intact when possible. All the constants/methods/events 
> have been updated and should be up-to-date with wxwidgets31 and 
> Scintilla 3.6.3.

It turned out that my patch for Scintilla 3.6.3 was not merged into
3.1.0 that was recently released, but has been merged into 3.1.1 (the current master branch), so I split the patch I had into two
branches/patches: wxwidgets310
(https://github.com/pkulchenko/wxlua/tree/wxwidgets310), which is updated for Scintilla 3.5.5 that was included with 3.1.0 and
wxwidgets311 (https://github.com/pkulchenko/wxlua/tree/wxwidgets311),
which includes Scintilla 3.6.3.

I plan on adding more missing methods/constants to 3.1.0 branch (and rebasing 3.1.1 branch to include Scintilla changes). Please let me know if you notice any issues with the bindings.

Paul.

On Tue, Feb 9, 2016 at 2:39 PM, Paul K <pau...@ya...> wrote:
> Hi All,
>
> For those interested in wxwidgets upgrades, I pulled the current 
> version of wxlua into a github repository and applied wxSTC changes in 
> the current wxwidgets master branch to wxlua; all these changes are 
> available in wxwidgets31 branch:
> https://github.com/pkulchenko/wxlua/tree/wxwidgets31
>
> I wrote a couple of scripts to merge stc.h constants/methods with 
> wxlua interface descriptions, but since the earlier changes have been 
> done manually, I've tried to reconcile the differences keeping the 
> manual changes intact when possible. All the constants/methods/events 
> have been updated and should be up-to-date with wxwidgets31 and 
> Scintilla 3.6.3.
>
> John, I also fixed an earlier change that removed CoffeeScript lexer 
> instead of removing just one constant in wxwidgets 3.1; the change is
> here: 
> https://github.com/pkulchenko/wxlua/commit/0cb663ecd05dd1aabe9dcd12a70
> 53f524dc336d5
>
> I've tested this with my application on Windows and would appreciate 
> you letting me know if you notice any issues with the updated binding.
>
> Paul.

------------------------------------------------------------------------------
_______________________________________________
wxlua-users mailing list
wxl...@li...
https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] About Alien.Lua

[Hernan C. <jhe...@gm...>]

Yes, John.
Thanks.

2016-03-14 15:25 GMT-05:00 John Labenski:

> wxLua does not use alien at all and I do now know where you may be able to
> find these DLLs.
>
> Good luck,
>      John
>
>

Re: [wxlua-users] About Alien.Lua

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

wxLua does not use alien at all and I do now know where you may be able to
find these DLLs.

Good luck,
     John


On Sat, Mar 12, 2016 at 10:30 AM, Hernan Cano <jhe...@gm...>
wrote:

> Hi, friend.
>
> I have downloaded
> https://github.com/torch/luarocks-mirror/blob/master/rocks/alien-0.7.0-1.src.rock
> but it lacks cre.dll and struct.dll .
>
> Can you say me where can I get these two DLLs and/or how could I compile
> this download for getting the both of them?
>
> Thanks.
>
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>

[wxlua-users] About Alien.Lua

[Hernan C. <jhe...@gm...>]

Hi, friend.

I have downloaded
https://github.com/torch/luarocks-mirror/blob/master/rocks/alien-0.7.0-1.src.rock
but it lacks cre.dll and struct.dll .

Can you say me where can I get these two DLLs and/or how could I compile
this download for getting the both of them?

Thanks.

Re: [wxlua-users] wxlua upgrade and outstanding issues

[Paul K <pau...@ya...>]

Hi All,

> manual changes intact when possible. All the constants/methods/events
> have been updated and should be up-to-date with wxwidgets31 and
> Scintilla 3.6.3.

It turned out that my patch for Scintilla 3.6.3 was not merged into
3.1.0 that was recently released, but has been merged into 3.1.1 (the
current master branch), so I split the patch I had into two
branches/patches: wxwidgets310
(https://github.com/pkulchenko/wxlua/tree/wxwidgets310), which is
updated for Scintilla 3.5.5 that was included with 3.1.0 and
wxwidgets311 (https://github.com/pkulchenko/wxlua/tree/wxwidgets311),
which includes Scintilla 3.6.3.

I plan on adding more missing methods/constants to 3.1.0 branch (and
rebasing 3.1.1 branch to include Scintilla changes). Please let me
know if you notice any issues with the bindings.

Paul.

On Tue, Feb 9, 2016 at 2:39 PM, Paul K <pau...@ya...> wrote:
> Hi All,
>
> For those interested in wxwidgets upgrades, I pulled the current
> version of wxlua into a github repository and applied wxSTC changes in
> the current wxwidgets master branch to wxlua; all these changes are
> available in wxwidgets31 branch:
> https://github.com/pkulchenko/wxlua/tree/wxwidgets31
>
> I wrote a couple of scripts to merge stc.h constants/methods with
> wxlua interface descriptions, but since the earlier changes have been
> done manually, I've tried to reconcile the differences keeping the
> manual changes intact when possible. All the constants/methods/events
> have been updated and should be up-to-date with wxwidgets31 and
> Scintilla 3.6.3.
>
> John, I also fixed an earlier change that removed CoffeeScript lexer
> instead of removing just one constant in wxwidgets 3.1; the change is
> here: https://github.com/pkulchenko/wxlua/commit/0cb663ecd05dd1aabe9dcd12a7053f524dc336d5
>
> I've tested this with my application on Windows and would appreciate
> you letting me know if you notice any issues with the updated binding.
>
> Paul.

Re: [wxlua-users] wxlua upgrade and outstanding issues

[Paul K <pau...@ya...>]

Hi All,

For those interested in wxwidgets upgrades, I pulled the current
version of wxlua into a github repository and applied wxSTC changes in
the current wxwidgets master branch to wxlua; all these changes are
available in wxwidgets31 branch:
https://github.com/pkulchenko/wxlua/tree/wxwidgets31

I wrote a couple of scripts to merge stc.h constants/methods with
wxlua interface descriptions, but since the earlier changes have been
done manually, I've tried to reconcile the differences keeping the
manual changes intact when possible. All the constants/methods/events
have been updated and should be up-to-date with wxwidgets31 and
Scintilla 3.6.3.

John, I also fixed an earlier change that removed CoffeeScript lexer
instead of removing just one constant in wxwidgets 3.1; the change is
here: https://github.com/pkulchenko/wxlua/commit/0cb663ecd05dd1aabe9dcd12a7053f524dc336d5

I've tested this with my application on Windows and would appreciate
you letting me know if you notice any issues with the updated binding.

Paul.

On Tue, Feb 2, 2016 at 11:29 AM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> wxwidgets team is getting ready to release v3.1.0 in about two weeks
> and it would be great to refresh the API in wxlua, fix some
> outstanding issues, and release the next version of wxlua. The upgrade
> will also include the latest Scintilla version (3.6.3), so it would be
> ideal to include added events/API calls as well. I tried to add some
> of them myself, but ran into issues even with simple methods like
> GetLibraryVersionInfo (it returns wxVersionInfo, which wxlua doesn't
> know about).
>
> Here are some of the recent discussions that may be relevant for the upgrade:
>
> 1. Memory leak in wxlua:
> http://sourceforge.net/p/wxlua/mailman/message/34430092/
> 2. MacOpenFiles and related methods:
> http://sourceforge.net/p/wxlua/mailman/message/34559782/
> 3. wxButton class is missing all the methods from wxAnyButton class
> it's inherited from
> (http://docs.wxwidgets.org/trunk/classwx_button.html). This affects
> methods like GetBitmap* and SetBitmap* as those are not present in
> wxButton (but rather inherited from wxAnyButton).
> 4. Several other methods missing:
> http://sourceforge.net/p/wxlua/mailman/message/32988247/
>
> There are likely to be more methods not in the bindings and I'm not
> sure what the best way to deal with those. Are you usually adding them
> manually? The more wxlua lags behind, the more difficult it becomes to
> add them. I've tried to go through 5k+ lines of stc.h to identify
> updated constants and methods, but there are just too many changes to
> do it manually; I considered writing a script, but there are also too
> many version-specific manual changes to make the script to work. I'm
> open to suggestions on how to proceed with these changes.
>
> In general, are you up for making some of these changes over the next
> 2-3 weeks? If not, I'll probably try to apply some of them myself (I
> have a clone of current wxlua code on github), but I have not been
> able to figure out how to fix the memory leak or how to support Mac*
> classes, so would welcome your assistance.
>
> Paul.

[wxlua-users] wxlua upgrade and outstanding issues

[Paul K <pau...@ya...>]

Hi John,

wxwidgets team is getting ready to release v3.1.0 in about two weeks
and it would be great to refresh the API in wxlua, fix some
outstanding issues, and release the next version of wxlua. The upgrade
will also include the latest Scintilla version (3.6.3), so it would be
ideal to include added events/API calls as well. I tried to add some
of them myself, but ran into issues even with simple methods like
GetLibraryVersionInfo (it returns wxVersionInfo, which wxlua doesn't
know about).

Here are some of the recent discussions that may be relevant for the upgrade:

1. Memory leak in wxlua:
http://sourceforge.net/p/wxlua/mailman/message/34430092/
2. MacOpenFiles and related methods:
http://sourceforge.net/p/wxlua/mailman/message/34559782/
3. wxButton class is missing all the methods from wxAnyButton class
it's inherited from
(http://docs.wxwidgets.org/trunk/classwx_button.html). This affects
methods like GetBitmap* and SetBitmap* as those are not present in
wxButton (but rather inherited from wxAnyButton).
4. Several other methods missing:
http://sourceforge.net/p/wxlua/mailman/message/32988247/

There are likely to be more methods not in the bindings and I'm not
sure what the best way to deal with those. Are you usually adding them
manually? The more wxlua lags behind, the more difficult it becomes to
add them. I've tried to go through 5k+ lines of stc.h to identify
updated constants and methods, but there are just too many changes to
do it manually; I considered writing a script, but there are also too
many version-specific manual changes to make the script to work. I'm
open to suggestions on how to proceed with these changes.

In general, are you up for making some of these changes over the next
2-3 weeks? If not, I'll probably try to apply some of them myself (I
have a clone of current wxlua code on github), but I have not been
able to figure out how to fix the memory leak or how to support Mac*
classes, so would welcome your assistance.

Paul.

Re: [wxlua-users] Building wxLua: missing wxWidgets libraries

[Hernan C. <jhe...@gm...>]

Hi, Valmir.

I'm interested also in bulding/compiling wxLua. It would be very pleasant
if you share how do you start or the doc you use for starting.

My goal is bulding/compiling using Lua 5.3 and Widgets 3.x (the last of
both) if possible. If any difficult, I would use the versions some one
recomend me.

Thanks.

HERNAN CANO M

Re: [wxlua-users] Building wxLua: missing wxWidgets libraries

[Valmir S. <Val...@hs...>]

Hi,

first thank you for the fast response.
After I switching from wxWidgets 3.0.x to 2.9.x version it can find all libraries and finally CMake build correctly the files.
As long I use the built-in Lua libraries everything seems to work fine, but when I try to build it against LuaJIT 2.0.4 (which use also LUA 5.1) I always get errors like:
…
2>           lbitlib.c
2>          Creating library C:/build/wxLua_build/lib/Release/wxlua-wx29mswu-2.8.12.3.lib and object C:/build/wxLua_build/lib/Release/wxlua-wx29mswu-2.8.12.3.exp
2>          wxlstate.obj : error LNK2019: unresolved external symbol luaopen_bit32 referenced in function "public: bool __cdecl wxLuaState::Create(struct lua_State *,int)" (?Create@wxLuaState@@QEAA_NPEAUlua_State@@H@Z)
2>          C:\build\wxLua_build\bin\Release\wxlua-wx29mswu-2.8.12.3.dll : fatal error LNK1120: 1 unresolved externals

Do you have an idea why this error comes up?


Thank you!
Best regards,
valmir

From: Joris Lambrecht [mailto:jor...@gm...]
Sent: Donnerstag, 7. Januar 2016 08:43
To: wxl...@li...
Subject: Re: [wxlua-users] Building wxLua: missing wxWidgets libraries


The answer is in the CMAKE file ... see help above .... you did not install or make the path available ....

Op wo 6 jan. 2016 16:50 schreef Valmir Sadiku <Val...@hs...<mailto:Val...@hs...>>:
Hello to all,

I’m new to wxLua and maybe (hopefully☺) this is not a hard question for you!

Building wxLua actually fails due some missing wxWidgets libraries.
The strange think is that they can find some of the libraries but not all, even all libraries are placed there.
Enclosed you can find the output from CMake (CMake_isssue.txt) and hopefully all information which you need to help me.
Building the wxWidgets seems to be okay, since I was able to run the samples (widgets, mediaplayer) .
Do you have an idea what could be the reason for that?

Thank you in advance!

Best regards,
valmir
------------------------------------------------------------------------------
_______________________________________________
wxlua-users mailing list
wxl...@li...<mailto:wxl...@li...>
https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Building wxLua: missing wxWidgets libraries

[Joris L. <jor...@gm...>]

The answer is in the CMAKE file ... see help above .... you did not install
or make the path available ....

Op wo 6 jan. 2016 16:50 schreef Valmir Sadiku <Val...@hs...>:

> Hello to all,
>
>
>
> I’m new to wxLua and maybe (hopefullyJ) this is not a hard question for
> you!
>
>
>
> Building wxLua actually fails due some missing wxWidgets libraries.
>
> The strange think is that they can find some of the libraries but not all,
> even all libraries are placed there.
>
> Enclosed you can find the output from CMake (CMake_isssue.txt) and
> hopefully all information which you need to help me.
>
> Building the wxWidgets seems to be okay, since I was able to run the
> samples (widgets, mediaplayer) .
>
> Do you have an idea what could be the reason for that?
>
>
>
> Thank you in advance!
>
>
>
> Best regards,
>
> valmir
>
> ------------------------------------------------------------------------------
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

[wxlua-users] Building wxLua: missing wxWidgets libraries

[Valmir S. <Val...@hs...>]

CMake Warning (dev) in CMakeLists.txt:
  Syntax Warning in cmake code at

    C:/build/wxLua-2.8.12.3-src/CMakeLists.txt:380:18

  Argument not separated from preceding token by whitespace.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) in CMakeLists.txt:
  Syntax Warning in cmake code at

    C:/build/wxLua-2.8.12.3-src/CMakeLists.txt:380:24

  Argument not separated from preceding token by whitespace.
This warning is for project developers.  Use -Wno-dev to suppress it.

* ---------------------------------------------------------------------------
* CMake command line options and tips specific to this project 
* 
* In the CMake GUI you can set values and press configure a few times 
* and until there are no more red items, then press generate.
* 
* Usage: cmake -D[OPTION_NAME]=[OPTION_VALUE] /path/to/CMakeLists.txt/
* ---------------------------------------------------------------------------
* -DHELP=TRUE 
*   Show this help message and exit, no files will be generated.
* -DCMAKE_BUILD_TYPE=[Debug, Release, RelWithDebInfo, MinSizeRel] : (Default Debug)
*   Makefiles : You must set the build type to Debug, Release...
*   MSVC GUI  : No need to set this since you can choose it in the GUI.
* -DBUILD_SHARED_LIBS=[TRUE, FALSE] : (Default static in MSW, shared in Linux)
*   Build shared (.DLL or .so) or static (.lib or .a) libraries.
* ---------------------------------------------------------------------------
 
 
*****************************************************************************
* BUILD TYPE:        Release
* BUILD_SHARED_LIBS: OFF
*****************************************************************************
* System is 32-bit FALSE, is 64-bit TRUE
*****************************************************************************
* CMAKE_SOURCE_DIR = C:/build/wxLua-2.8.12.3-src
* CMAKE_BINARY_DIR = C:/build/wxLua_build
*****************************************************************************
 
* ---------------------------------------------------------------------------
* wxWidgets library settings :
* 
* Note that ONLY an all shared (DLL) or all static build is supported.
*   I.E. If you choose shared you must link to shared wxWidgets libs.
*   Set -DBUILD_SHARED_LIBS=[TRUE, FALSE] to control shared/static lib.
* 
* Finding wxWidgets for MSW and MSVC
* -DwxWidgets_ROOT_DIR=[path] : (e.g. /path/to/wxWidgets/)
*   Path to the root of the wxWidgets build, must at least set this.
* -DwxWidgets_LIB_DIR=[path] : (e.g. /path/to/wxWidgets/lib/vc_lib/)
*   Path to the wxWidgets lib dir also set this if libs can't be found.
* -DwxWidgets_CONFIGURATION=[configuration] : 
*   Set wxWidgets configuration; e.g. msw, mswu, mswunivu...
*   Where 'u' = unicode and 'd' = debug.
*   MSVC GUI : You need only choose msw, mswu, mswuniv, mswunivu since 
*              release or debug mode is chosen in the GUI.
* -DwxWidgets_COMPONENTS=[...stc;html;adv;core;base or mono] : 
*   For non-monolithic builds choose the wxWidgets libs to link to.
*    xrc;xml;gl;net;media;propgrid;richtext;aui;stc;html;adv;core;base
*   For monolithic builds choose mono and the contribs libs.
*    stc;mono
*   The extra decorations, e.g. wxmsw28ud_adv.lib, will be searched for.
*   Libs that cannot be found will be printed below, please fix/remove
*   them to be able to build this project.
*   You will get compilation/linker errors if wxWidgets is not found.
* 
* Finding wxWidgets for GCC and Unix type systems
* -DwxWidgets_CONFIG_EXECUTABLE=[path/to/wx-config] : 
*   Specify path to wx-config script for GCC and Unix type builds
* ---------------------------------------------------------------------------
 
* Using these wxWidgets components: gl;xrc;xml;net;media;richtext;aui;html;adv;core;base
Could NOT find wxWidgets (missing:  wxWidgets_FOUND) 
* 
CMake Warning at build/CMakewxAppLib.cmake:313 (message):
  * WARNING: Could not find wxWidgets! Please see help above.
Call Stack (most recent call first):
  CMakeLists.txt:54 (FIND_WXWIDGETS)


* - wxWidgets_VERSION           = 3.0.2 = 3.0.2
* - wxWidgets_COMPONENTS        = gl;xrc;xml;net;media;richtext;aui;html;adv;core;base
* - wxWidgets_INCLUDE_DIRS      = C:/build/wxWidgets-3.0.2/lib/vc_x64_lib/mswu;C:/build/wxWidgets-3.0.2/include
* - wxWidgets_LIBRARY_DIRS      = C:/build/wxWidgets-3.0.2/lib/vc_x64_lib
* - wxWidgets_LIBRARIES         = C:/build/wxWidgets-3.0.2/lib/vc_x64_lib/wxpng.lib;C:/build/wxWidgets-3.0.2/lib/vc_x64_lib/wxtiff.lib;C:/build/wxWidgets-3.0.2/lib/vc_x64_lib/wxjpeg.lib;C:/build/wxWidgets-3.0.2/lib/vc_x64_lib/wxzlib.lib;C:/build/wxWidgets-3.0.2/lib/vc_x64_lib/wxregexu.lib;C:/build/wxWidgets-3.0.2/lib/vc_x64_lib/wxexpat.lib;opengl32;glu32;winmm;comctl32;rpcrt4;wsock32
* - wxWidgets_CXX_FLAGS         = 
* - wxWidgets_DEFINITIONS       = UNICODE;_UNICODE
* - wxWidgets_DEFINITIONS_DEBUG = _DEBUG;__WXDEBUG__
* - wxWidgets_PORTNAME          = 
* - wxWidgets_UNIVNAME          = 
* - wxWidgets_UNICODEFLAG       = 
* - wxWidgets_DEBUGFLAG         = 
 WARNING: Unable to find requested wxWidgets component : gl
 WARNING: Unable to find requested wxWidgets component : xrc
 WARNING: Unable to find requested wxWidgets component : xml
 WARNING: Unable to find requested wxWidgets component : net
 WARNING: Unable to find requested wxWidgets component : media
 WARNING: Unable to find requested wxWidgets component : richtext
 WARNING: Unable to find requested wxWidgets component : aui
 WARNING: Unable to find requested wxWidgets component : html
 WARNING: Unable to find requested wxWidgets component : adv
 WARNING: Unable to find requested wxWidgets component : core
 WARNING: Unable to find requested wxWidgets component : base
* 
wxWidgets requested but not found.
* WARNING: Specified wxLuaBinding lib 'stc' in variable wxLuaBind_COMPONENTS is missing from wxWidgets_COMPONENTS so it will not be compiled.
* WARNING: Specified wxLuaBinding lib 'propgrid' in variable wxLuaBind_COMPONENTS is missing from wxWidgets_COMPONENTS so it will not be compiled.
* wxLua using external/system Lua library :
*   - include dir : C:/build/LuaJIT-2.0.4/src
*   - library     : C:/build/LuaJIT-2.0.4/src/lua51.lib
* Not copying the Lua proxydlls since they do not work in the 64-bit build.
Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE) 
* WARNING: Doxygen NOT found, wxLua_doxygen target will not be generated.
wxWidgets requested but not found.
Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE) 
* WARNING: Doxygen NOT found, wxStEdit_doxygen target will not be generated.
CMake Warning (dev) at build/CMakeFunctions.cmake:1225 (elseif):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "PROPERTIES" will no longer be dereferenced when the
  policy is set to NEW.  Since the policy is not set the OLD behavior will be
  used.
Call Stack (most recent call first):
  build/CMakeFunctions.cmake:1516 (APPEND_SOURCE_FILES_PROPERTIES)
  build/CMakeFunctions.cmake:872 (TARGET_PRECOMPILED_HEADER)
  modules/wxstedit/CMakeLists.txt:99 (ADD_LIBRARY_FULL)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at build/CMakeFunctions.cmake:988 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "WIN32" will no longer be dereferenced when the
  policy is set to NEW.  Since the policy is not set the OLD behavior will be
  used.
Call Stack (most recent call first):
  modules/wxstedit/CMakeLists.txt:208 (ADD_EXECUTABLE_FULL)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at build/CMakeFunctions.cmake:988 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "WIN32" will no longer be dereferenced when the
  policy is set to NEW.  Since the policy is not set the OLD behavior will be
  used.
Call Stack (most recent call first):
  apps/CMakeLists.txt:27 (ADD_EXECUTABLE_FULL)
  apps/wxlua/CMakeLists.txt:3 (wxLua_Apps_wxLua_TARGETS)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at build/CMakeFunctions.cmake:988 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "WIN32" will no longer be dereferenced when the
  policy is set to NEW.  Since the policy is not set the OLD behavior will be
  used.
Call Stack (most recent call first):
  apps/CMakeLists.txt:56 (ADD_EXECUTABLE_FULL)
  apps/wxluacan/CMakeLists.txt:3 (wxLua_Apps_wxLuaCan_TARGETS)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at build/CMakeFunctions.cmake:988 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "WIN32" will no longer be dereferenced when the
  policy is set to NEW.  Since the policy is not set the OLD behavior will be
  used.
Call Stack (most recent call first):
  apps/CMakeLists.txt:98 (ADD_EXECUTABLE_FULL)
  apps/wxluaedit/CMakeLists.txt:3 (wxLua_Apps_wxLuaEdit_TARGETS)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at build/CMakeFunctions.cmake:988 (if):
  Policy CMP0054 is not set: Only interpret if() arguments as variables or
  keywords when unquoted.  Run "cmake --help-policy CMP0054" for policy
  details.  Use the cmake_policy command to set the policy and suppress this
  warning.

  Quoted variables like "WIN32" will no longer be dereferenced when the
  policy is set to NEW.  Since the policy is not set the OLD behavior will be
  used.
Call Stack (most recent call first):
  apps/CMakeLists.txt:131 (ADD_EXECUTABLE_FULL)
  apps/wxluafreeze/CMakeLists.txt:3 (wxLua_Apps_wxLuaFreeze_TARGETS)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at bindings/CMakeLists.txt:152 (get_target_property):
  Policy CMP0045 is not set: Error on non-existent target in
  get_target_property.  Run "cmake --help-policy CMP0045" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  get_target_property() called with non-existent target "lua".
Call Stack (most recent call first):
  bindings/CMakeLists.txt:183 (ADD_WXLUABIND_GENERATION)
This warning is for project developers.  Use -Wno-dev to suppress it.

Configuring done

[wxlua-users] Ejecutar varias versiones de Lua en el mismo computador

[Hernan C. <jhe...@gm...>]

Hola, amigo.

Quisiera saber si puedes ayudarme con el sgte escenario:

Estoy interesado en usar wxLua, Lua y Widgets. Pero wxLua sólo ejecuta en
Lua 5.1, aunque hay algún intento documentado para compilarse en Lua 5.2
(que analizaré mucho más adelante). Actualmente la última versión de Lua es
la 5.3.

En lo personal no quisiera tener que "compilar Lua, Widgets y wxLua", pero
así es el FLOSS, así que debo avanzar y me interesa hacerlo de esta forma:

Como me interesa usar wxLua/wxWidgets con la última versión de Lua (la
5.3), entonces el escenario que deseo lo describo así:

*Tener Lua 5.1*, porque sólo en él es que funciona wxLua 2.8.
*Tener Lua 5.2*, porque hay un intento documentado por parte de los
creadores de wxLua para compilarlo en esta versión.
*Tener Lua 5.3*, porque es la última versión y es el que deseo usar en
última instancia.

Mi consulta es:
*¿Cómo debo configurar mi sistema (mi PC) para ejecutar las tres versiones
de Lua* y los ejemplos de Lua de las tres versiones y algún programa mío en
Lua que pueda ser ejecutado en todas las versiones?

Te comento que conozco las variables de ambiente LUA_DEV y LUA_PATH, pero
evidentemente si las creo tendría conflictos con las otras versiones
(¿cierto? En mi sistema tengo instalado Lua for Windows y creo ---creo
yo--- que por éso es que sólo todo sólo me funciona en Lua 5.1).

Pienso instalar (¿o copiar?) las versiones de Lua más o menos así:

*C:\Lua*
     *Lua51*
       lib
   clibs
   utils
   metalua.bat
       ilua.cmd
       7z.dll
       lua5.1.dll
       lua51.dll
       7z.exe
       bin2c.exe
       lua.exe
       luac.exe
       luafw.exe
       wlua.exe
       luarocks.lua
       luarocks_config.lua
       luarocks-admin.lua
       lExecutor.wlua

     *Lua52*
       dll_dyn
       lua5.2.dll
       lua52.dll
       lua52.exe
       luac52.exe
       wlua52.exe

     *Lua53*
       lua53.dll
       wx.dll
       lua53.exe
       luac53.exe
       wlua53.exe
       minimal.wx.lua
       tree.wx.lua

*C:\Lua_Ejemplos*
       *.lua

Y ejecutar los ejemplos más o menos así:

cd C:\Lua_Ejemplos
C:\Lua\Lua52\lua52.exe ejemplo1.lua
C:\Lua\Lua53\lua53.exe ejemplo1.lua
C:\Lua\Lua51\lua.exe   ejemplo1.lua

Agradezco si me puedes resolver esta inquietud.

Gracias.

*HERNAN CANO MARTINEZ*
Systems Analyst - Programmer
Medellín, Colombia.

[wxlua-users] Programming in Lua with Widgets

[Hernan C. <jhe...@gm...>]

Hi, friends.

I am interested in programming in Lua, and enhance it with Widgets.
But I feel no confortable with having to compile (build) so many things
around.

Could you help me to...

1. I would like to use the last version on Lua and Widgets. But it seems
that wxLua (a good work for this objective) only runs in Lua 5.1.

2. I do not want to compile Lua 5.3 (nor any version of Lua). I will use a
binary available in Internet.
   I do not want to compile Widgets 3.xxx last version (nor any version of
Widgets that can be used with Lua). I will use a binary available in
Internet.

3. Compile wxLua? I have MS-VC++ 2008 Express (unfortunately) and also
MinGW32. CodeLite if somebody want to help me.
   Please I am not expert in VS nor I use it frequently.... but I'll
receive instructions.

4. My main goal is: to use Widgets last version with Lua last version and
that I can change the main executable of Lua when a new version come; and
same for Widgets.

For what I have read, it seems that thhis is not possible or it is very
difficult (for some whow knows about Lua, C/C++, compiling, bulding and
Widgets).
But Paul Kulchenko in
https://stackoverflow.com/questions/29457710/compiling-wxlua-cross-platform-static
says that it is possible to compile wxLua in Lua 5.2... and then I would
want to try it... after directions from all of you.

5. I want to have several version of Lua: 5.1 (because wxLua only run in
this for now), 5.3 (because it is the last) and 5.2 (for a wide range of
the knowledge --if I can execute in all of the three, I will have a good
understand of this theme/thing--).

For this I know I must not use the LUA_DEV or LUA_PATH sysvars. And for
this thing I want your instructions.

Waiting for your kind helping,

*HERNAN CANO MARTINEZ*
Systems Analyst - Programmer
Medellín, Colombia.

Re: [wxlua-users] Running a .wx.lua.....

[Hernan C. <jhe...@gm...>]

Thanks, Victor.
I will digest this information.
By.

2015-11-19 13:49 GMT-05:00 Victor Bombi:

> Hi Hernan,
> luajit http://luajit.org/ is a just in time compiler (JIT) for lua, that
> means that you get machine code (as in a C or C++ source compiled) from lua
> which is faster (http://luajit.org/performance_x86.html) than pure Lua
> virtual machine code.
> Besides that, luajit gives you FFI (http://luajit.org/ext_ffi.html) which
> lets you use any module (.dll or .so) that is exporting functions from Lua
> directly without having to compile a Lua binding for that.
> Best
> victor
>
>
>

Re: [wxlua-users] Running a .wx.lua.....

[Victor B. <so...@te...>]

Hi Hernan,
luajit http://luajit.org/ is a just in time compiler (JIT) for lua, that means that you get machine code (as in a C or C++ source compiled) from lua which is faster (http://luajit.org/performance_x86.html) than pure Lua virtual machine code.
Besides that, luajit gives you FFI (http://luajit.org/ext_ffi.html) which lets you use any module (.dll or .so) that is exporting functions from Lua directly without having to compile a Lua binding for that.
Best
victor
  ----- Original Message ----- 
  From: Hernan Cano 
  To: Victor Bombi 
  Sent: Thursday, November 19, 2015 12:05 AM
  Subject: Re: [wxlua-users] Running a .wx.lua.....


  Hi, Victor.
  Thanks for answering.


  I am very interested in wxLua.


  If you can say me something about LuaJIT (that I could understand), I appreciate it.


  By.



  2015-11-18 11:05 GMT-05:00 Victor Bombi:

    But did you know that using lua53 you loose luajit...?
      ----- Original Message -----
      From: Hernan Cano
      To: undisclosed-recipients
      Sent: Sunday, November 15, 2015 4:15 AM
      Subject: [wxlua-users] Running a .wx.lua.....


      Hello, friends.


      I am initiating in wxLua, that is Lua with Widgets.


      I can run a .lua with lua51 and lua53. I am interested in Lua53.


      I can run a .wx.lua with lua51, but not with lua53, but I am interested in lua53.


      Can you tell me how can I run the wxLua examples in lua v5.3?


      Thank you.


      HERNAN CANO M.
      Systems Analyst - Programmer


--------------------------------------------------------------------------

Re: [wxlua-users] Running a .wx.lua.....

[Victor B. <so...@te...>]

But did you know that using lua53 you loose luajit...?
  ----- Original Message ----- 
  From: Hernan Cano 
  To: undisclosed-recipients
  Sent: Sunday, November 15, 2015 4:15 AM
  Subject: [wxlua-users] Running a .wx.lua.....


  confirm 2d3d812c0ac3bb262df0416eda96a24521da9475

  Hello, friends.


  I am initiating in wxLua, that is Lua with Widgets.


  I can run a .lua with lua51 and lua53. I am interested in Lua53.


  I can run a .wx.lua with lua51, but not with lua53, but I am interested in lua53.


  Can you tell me how can I run the wxLua examples in lua v5.3?


  Thank you.


  HERNAN CANO M.
  Systems Analyst - Programmer




------------------------------------------------------------------------------


  ------------------------------------------------------------------------------



------------------------------------------------------------------------------


  _______________________________________________
  wxlua-users mailing list
  wxl...@li...
  https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Memory leak on checking for non-existing fields

[Paul K <pau...@ya...>]

Hi John,

I ran my sample script through valgrind and it confirmed that the
leaked memory is what's being used for strings in error messages. I'm
including relevant parts of valgrind reports for different error
conditions, but it turned out to be leaking more memory than I thought
(1.6k per error message). Since the error is generated each time there
is a check for a non-existing field it adds up quickly as there is no
other way to check if a field is present on wxlua object or not.

I think the final error message in wxlua_wxLuaBindClass__index is
unnecessary; without it it would behave exactly as Lua method/field
calls behave in all other places:

> wx.wxTextCtrl().Absent()
[string "wx.wxTextCtrl().Absent()"]:1: attempt to call field 'Absent'
(a nil value)
> wx.wxTextCtrl():Absent()
[string "wx.wxTextCtrl():Absent()"]:1: attempt to call method 'Absent'
(a nil value)
> wx.wxTextCtrl().Absent
nil

Here is the simple patch I'm proposing:

diff --git a/wxLua/modules/wxlua/wxlbind.cpp b/wxLua/modules/wxlua/wxlbind.cpp
index 105f603..2523292 100644
--- a/wxLua/modules/wxlua/wxlbind.cpp
+++ b/wxLua/modules/wxlua/wxlbind.cpp
@@ -227,12 +227,6 @@ int LUACALL wxlua_wxLuaBindClass__index(lua_State *L)
         }
     }

-    if (!found)
-    {
-        wxlua_error(L, wxString::Format(_("wxLua: Unable to call an
unknown method '%s' on a '%s' type."),
-            lua2wx(name).c_str(), lua2wx(wxlClass ? wxlClass->name :
"").c_str()).c_str());
-    }
-
     return result;
 }

This doesn't fix the leak directly, but it eliminates one of the main
cases that make the leak much more noticeable.

I'm including reports for two conditions: incorrect parameters
(wx.wxTextCtrl().DiscardEdits()) and non-string as the key
(wx.wxTextCtrl()[{}]). They follow different branches, but leak about
the same amount of memory.

Paul.

require "wx"
local ctrl = wx.wxTextCtrl()
for _ = 1, 1000 do pcall(function() return ctrl.DiscardEdits() end) end

==2610== 48,000 bytes in 1,000 blocks are definitely lost in loss
record 3,788 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE85BE: wchar_t* std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_S_construct<wchar_t const*>(wchar_t const*, wchar_t const*,
std::allocator<wchar_t> const&, std::forward_iterator_tag) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE8736: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::basic_string(wchar_t const*, std::allocator<wchar_t> const&) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4B5F018: wxString::wxString(char const*, wxMBConv
const&) (in /home/paul/zbs/bin/linux/x86/libwx.so)
==2610==    by 0x4B605CA: lua2wx(char const*) (wxllua.h:41)
==2610==    by 0x4BB7969: wxlua_luaL_typename(lua_State*, int) (wxllua.cpp:939)
==2610==    by 0x4BB50D6: wxlua_argerror(lua_State*, int, wxString
const&) (wxllua.cpp:169)
==2610==    by 0x4BB7D3E: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==    by 0x805813A: ??? (in /usr/bin/lua5.1)
==2610==
==2610== 56,000 bytes in 1,000 blocks are definitely lost in loss
record 3,789 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE85BE: wchar_t* std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_S_construct<wchar_t const*>(wchar_t const*, wchar_t const*,
std::allocator<wchar_t> const&, std::forward_iterator_tag) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE8736: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::basic_string(wchar_t const*, std::allocator<wchar_t> const&) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4B5F018: wxString::wxString(char const*, wxMBConv
const&) (in /home/paul/zbs/bin/linux/x86/libwx.so)
==2610==    by 0x4B605CA: lua2wx(char const*) (wxllua.h:41)
==2610==    by 0x4BB786F: wxluaT_typename(lua_State*, int) (wxllua.cpp:925)
==2610==    by 0x4BB7CE4: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==    by 0x805813A: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2610==
==2610== 68,000 bytes in 1,000 blocks are definitely lost in loss
record 3,790 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE768F: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_M_clone(std::allocator<wchar_t> const&, unsigned int) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE77BD: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::reserve(unsigned
int) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4E4F2B0: reserve (string.h:1332)
==2610==    by 0x4E4F2B0: Alloc (string.h:2195)
==2610==    by 0x4E4F2B0: operator+(wchar_t const*, wxString const&)
(string.cpp:695)
==2610==    by 0x4BB7D03: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==    by 0x805813A: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804BAFF: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804E8F1: ??? (in /usr/bin/lua5.1)
==2610==
==2610== 72,000 bytes in 1,000 blocks are definitely lost in loss
record 3,791 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE768F: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_M_clone(std::allocator<wchar_t> const&, unsigned int) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE77BD: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::reserve(unsigned
int) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4E4F1D8: reserve (string.h:1332)
==2610==    by 0x4E4F1D8: Alloc (string.h:2195)
==2610==    by 0x4E4F1D8: operator+(wxString const&, wchar_t const*)
(string.cpp:663)
==2610==    by 0x4BB7D22: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==    by 0x805813A: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804BAFF: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804E8F1: ??? (in /usr/bin/lua5.1)
==2610==
==2610== 119,880 bytes in 999 blocks are definitely lost in loss
record 3,792 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE768F: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_M_clone(std::allocator<wchar_t> const&, unsigned int) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE77BD: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::reserve(unsigned
int) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE7B0F: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::append(wchar_t
const*, unsigned int) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE7C25: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::operator+=(wchar_t const*) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4B979A7: wxString::operator+=(wchar_t const*) (string.h:3237)
==2610==    by 0x4BADC68: wxlua_getLuaArgsMsg(lua_State*, int, int)
(wxlbind.cpp:592)
==2610==    by 0x4BB52D3: wxlua_argerrormsg(lua_State*, wxString
const&) (wxllua.cpp:180)
==2610==    by 0x4BB51B7: wxlua_argerror(lua_State*, int, wxString
const&) (wxllua.cpp:174)
==2610==    by 0x4BB7D3E: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==
==2610== 151,000 bytes in 1,000 blocks are definitely lost in loss
record 3,793 of 3,796
==2610==    at 0x402C619: malloc (vg_replace_malloc.c:299)
==2610==    by 0x402C79F: realloc (vg_replace_malloc.c:785)
==2610==    by 0x4E4EF97: Extend (string.h:3329)
==2610==    by 0x4E4EF97: wxString::AsChar(wxMBConv const&) const
(string.cpp:545)
==2610==    by 0x4A61573: wxCStrData::AsChar() const (string.h:4038)
==2610==    by 0x4A61542: wxCStrData::operator char const*() const
(string.h:166)
==2610==    by 0x4BB543B: wxlua_argerrormsg(lua_State*, wxString
const&) (wxllua.cpp:202)
==2610==    by 0x4BB51B7: wxlua_argerror(lua_State*, int, wxString
const&) (wxllua.cpp:174)
==2610==    by 0x4BB7D3E: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==    by 0x805813A: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2610==
==2610== 203,796 bytes in 999 blocks are definitely lost in loss
record 3,794 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE768F: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_M_clone(std::allocator<wchar_t> const&, unsigned int) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE77BD: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t> >::reserve(unsigned
int) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE7D86: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::append(std::basic_string<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> > const&) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x5DE7E12: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::operator+=(std::basic_string<wchar_t, std::char_traits<wchar_t>,
std::allocator<wchar_t> > const&) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4B908C1: wxString::operator+=(wxString const&) (string.h:3222)
==2610==    by 0x4BB5355: wxlua_argerrormsg(lua_State*, wxString
const&) (wxllua.cpp:197)
==2610==    by 0x4BB51B7: wxlua_argerror(lua_State*, int, wxString
const&) (wxllua.cpp:174)
==2610==    by 0x4BB7D3E: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==
==2610== 292,000 bytes in 1,000 blocks are definitely lost in loss
record 3,795 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4E4F028:
_S_construct<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.tcc:140)
==2610==    by 0x4E4F028:
_S_construct_aux<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.h:1692)
==2610==    by 0x4E4F028:
_S_construct<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.h:1713)
==2610==    by 0x4E4F028:
basic_string<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.tcc:231)
==2610==    by 0x4E4F028: wxString (string.h:2271)
==2610==    by 0x4E4F028: wxString::Shrink() (string.cpp:562)
==2610==    by 0x4E516CA: DoStringPrintfV(wxString&, wxString const&,
char*) (string.cpp:2119)
==2610==    by 0x4E517FE: wxString::DoFormatWchar(wchar_t const*, ...)
(string.cpp:1893)
==2610==    by 0x4BA0259: wxString wxString::Format<wxCStrData, int,
wxCStrData>(wxFormatString const&, wxCStrData, int, wxCStrData)
(string.h:2188)
==2610==    by 0x4BB516B: wxlua_argerror(lua_State*, int, wxString
const&) (wxllua.cpp:172)
==2610==    by 0x4BB7D3E: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==    by 0x805813A: ??? (in /usr/bin/lua5.1)
==2610==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2610==
==2610== 613,536 bytes in 996 blocks are definitely lost in loss
record 3,796 of 3,796
==2610==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2610==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2610==    by 0x4E4F028:
_S_construct<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.tcc:140)
==2610==    by 0x4E4F028:
_S_construct_aux<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.h:1692)
==2610==    by 0x4E4F028:
_S_construct<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.h:1713)
==2610==    by 0x4E4F028:
basic_string<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.tcc:231)
==2610==    by 0x4E4F028: wxString (string.h:2271)
==2610==    by 0x4E4F028: wxString::Shrink() (string.cpp:562)
==2610==    by 0x4E516CA: DoStringPrintfV(wxString&, wxString const&,
char*) (string.cpp:2119)
==2610==    by 0x4E51739: wxString::DoPrintfWchar(wchar_t const*, ...)
(string.cpp:1944)
==2610==    by 0x4BBB1B6: int wxString::Printf<wxCStrData, wxCStrData,
wxCStrData>(wxFormatString const&, wxCStrData, wxCStrData, wxCStrData)
(string.h:2181)
==2610==    by 0x4BB53EC: wxlua_argerrormsg(lua_State*, wxString
const&) (wxllua.cpp:201)
==2610==    by 0x4BB51B7: wxlua_argerror(lua_State*, int, wxString
const&) (wxllua.cpp:174)
==2610==    by 0x4BB7D3E: wxluaT_getuserdatatype(lua_State*, int, int)
(wxllua.cpp:1093)
==2610==    by 0x4AAF381: wxLua_wxTextCtrl_DiscardEdits(lua_State*)
(wxcore_controls.cpp:8270)
==2610==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2610==    by 0x805813A: ??? (in /usr/bin/lua5.1)
==2610==
==2610== LEAK SUMMARY:
==2610==    definitely lost: 1,628,352 bytes in 9,061 blocks
==2610==    indirectly lost: 3,264 bytes in 75 blocks
==2610==      possibly lost: 247,502 bytes in 2,140 blocks

require "wx"
local ctrl = wx.wxTextCtrl()
for _ = 1, 1000 do pcall(function() return ctrl[{}] end) end

==2635== 36,000 bytes in 1,000 blocks are definitely lost in loss
record 3,786 of 3,792
==2635==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2635==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x5DE85BE: wchar_t* std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_S_construct<wchar_t const*>(wchar_t const*, wchar_t const*,
std::allocator<wchar_t> const&, std::forward_iterator_tag) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x5DE8736: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::basic_string(wchar_t const*, std::allocator<wchar_t> const&) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x4B5F018: wxString::wxString(char const*, wxMBConv
const&) (in /home/paul/zbs/bin/linux/x86/libwx.so)
==2635==    by 0x4B605CA: lua2wx(char const*) (wxllua.h:41)
==2635==    by 0x4BB7969: wxlua_luaL_typename(lua_State*, int) (wxllua.cpp:939)
==2635==    by 0x4BABB39: wxlua_wxLuaBindClass__index(lua_State*)
(wxlbind.cpp:143)
==2635==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F567: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8056783: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8057A00: ??? (in /usr/bin/lua5.1)
==2635==
==2635== 56,000 bytes in 1,000 blocks are definitely lost in loss
record 3,787 of 3,792
==2635==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2635==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x5DE85BE: wchar_t* std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_S_construct<wchar_t const*>(wchar_t const*, wchar_t const*,
std::allocator<wchar_t> const&, std::forward_iterator_tag) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x5DE8736: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::basic_string(wchar_t const*, std::allocator<wchar_t> const&) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x4B5F018: wxString::wxString(char const*, wxMBConv
const&) (in /home/paul/zbs/bin/linux/x86/libwx.so)
==2635==    by 0x4B605CA: lua2wx(char const*) (wxllua.h:41)
==2635==    by 0x4BABAFE: wxlua_wxLuaBindClass__index(lua_State*)
(wxlbind.cpp:143)
==2635==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F567: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8056783: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8057A00: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2635==
==2635== 82,000 bytes in 1,000 blocks are definitely lost in loss
record 3,788 of 3,792
==2635==    at 0x402C619: malloc (vg_replace_malloc.c:299)
==2635==    by 0x402C79F: realloc (vg_replace_malloc.c:785)
==2635==    by 0x4E4EF97: Extend (string.h:3329)
==2635==    by 0x4E4EF97: wxString::AsChar(wxMBConv const&) const
(string.cpp:545)
==2635==    by 0x4A61573: wxCStrData::AsChar() const (string.h:4038)
==2635==    by 0x4A61542: wxCStrData::operator char const*() const
(string.h:166)
==2635==    by 0x4BABBFF: wxlua_wxLuaBindClass__index(lua_State*)
(wxlbind.cpp:143)
==2635==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F567: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8056783: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8057A00: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804BAFF: ??? (in /usr/bin/lua5.1)
==2635==
==2635== 296,000 bytes in 1,000 blocks are definitely lost in loss
record 3,789 of 3,792
==2635==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2635==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x5DE85BE: wchar_t* std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_S_construct<wchar_t const*>(wchar_t const*, wchar_t const*,
std::allocator<wchar_t> const&, std::forward_iterator_tag) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x5DE8736: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::basic_string(wchar_t const*, std::allocator<wchar_t> const&) (in
/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x4A96C4C: wxString::wxString(char const*) (in
/home/paul/zbs/bin/linux/x86/libwx.so)
==2635==    by 0x4BABB7D: wxlua_wxLuaBindClass__index(lua_State*)
(wxlbind.cpp:142)
==2635==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F567: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8056783: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8057A00: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804BAFF: ??? (in /usr/bin/lua5.1)
==2635==
==2635== 340,000 bytes in 1,000 blocks are definitely lost in loss
record 3,790 of 3,792
==2635==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2635==    by 0x5DE6386: std::basic_string<wchar_t,
std::char_traits<wchar_t>, std::allocator<wchar_t>
>::_Rep::_S_create(unsigned int, unsigned int, std::allocator<wchar_t>
const&) (in /usr/lib/i386-linux-gnu/libstdc++.so.6.0.16)
==2635==    by 0x4E4F028:
_S_construct<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.tcc:140)
==2635==    by 0x4E4F028:
_S_construct_aux<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.h:1692)
==2635==    by 0x4E4F028:
_S_construct<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.h:1713)
==2635==    by 0x4E4F028:
basic_string<__gnu_cxx::__normal_iterator<const wchar_t*,
std::basic_string<wchar_t> > > (basic_string.tcc:231)
==2635==    by 0x4E4F028: wxString (string.h:2271)
==2635==    by 0x4E4F028: wxString::Shrink() (string.cpp:562)
==2635==    by 0x4E516CA: DoStringPrintfV(wxString&, wxString const&,
char*) (string.cpp:2119)
==2635==    by 0x4E517FE: wxString::DoFormatWchar(wchar_t const*, ...)
(string.cpp:1893)
==2635==    by 0x4B91292: wxString wxString::Format<wxCStrData,
wxCStrData>(wxFormatString const&, wxCStrData, wxCStrData)
(string.h:2188)
==2635==    by 0x4BABBD3: wxlua_wxLuaBindClass__index(lua_State*)
(wxlbind.cpp:143)
==2635==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F567: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8056783: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8057A00: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F5B7: ??? (in /usr/bin/lua5.1)
==2635==
==2635== 424,000 bytes in 1,000 blocks are indirectly lost in loss
record 3,791 of 3,792
==2635==    at 0x402C619: malloc (vg_replace_malloc.c:299)
==2635==    by 0x402C79F: realloc (vg_replace_malloc.c:785)
==2635==    by 0x4E52C07: wxCharTypeBuffer<wchar_t>::extend(unsigned
int) (buffer.h:324)
==2635==    by 0x4E52CF4:
wxFormatConverterBase<wchar_t>::CopyAllBefore() (strvararg.cpp:378)
==2635==    by 0x4E52D4F:
wxFormatConverterBase<wchar_t>::InsertFmtChar(wchar_t)
(strvararg.cpp:349)
==2635==    by 0x4E52F3C:
wxFormatConverterBase<wchar_t>::Convert(wchar_t const*)
(strvararg.cpp:270)
==2635==    by 0x4E52291: wxFormatString::AsWChar() (strvararg.cpp:643)
==2635==    by 0x4A3D4EE: wxFormatString::operator wchar_t const*()
const (strvararg.h:220)
==2635==    by 0x4B91279: wxString wxString::Format<wxCStrData,
wxCStrData>(wxFormatString const&, wxCStrData, wxCStrData)
(string.h:2188)
==2635==    by 0x4BABBD3: wxlua_wxLuaBindClass__index(lua_State*)
(wxlbind.cpp:143)
==2635==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F567: ??? (in /usr/bin/lua5.1)
==2635==
==2635== 436,000 (12,000 direct, 424,000 indirect) bytes in 1,000
blocks are definitely lost in loss record 3,792 of 3,792
==2635==    at 0x402C10B: operator new(unsigned int) (vg_replace_malloc.c:327)
==2635==    by 0x4E52C38: wxCharTypeBuffer<wchar_t>::extend(unsigned
int) (buffer.h:334)
==2635==    by 0x4E52CF4:
wxFormatConverterBase<wchar_t>::CopyAllBefore() (strvararg.cpp:378)
==2635==    by 0x4E52D4F:
wxFormatConverterBase<wchar_t>::InsertFmtChar(wchar_t)
(strvararg.cpp:349)
==2635==    by 0x4E52F3C:
wxFormatConverterBase<wchar_t>::Convert(wchar_t const*)
(strvararg.cpp:270)
==2635==    by 0x4E52291: wxFormatString::AsWChar() (strvararg.cpp:643)
==2635==    by 0x4A3D4EE: wxFormatString::operator wchar_t const*()
const (strvararg.h:220)
==2635==    by 0x4B91279: wxString wxString::Format<wxCStrData,
wxCStrData>(wxFormatString const&, wxCStrData, wxCStrData)
(string.h:2188)
==2635==    by 0x4BABBD3: wxlua_wxLuaBindClass__index(lua_State*)
(wxlbind.cpp:143)
==2635==    by 0x804F1CD: ??? (in /usr/bin/lua5.1)
==2635==    by 0x804F567: ??? (in /usr/bin/lua5.1)
==2635==    by 0x8056783: ??? (in /usr/bin/lua5.1)
==2635==
==2635== LEAK SUMMARY:
==2635==    definitely lost: 826,140 bytes in 6,067 blocks
==2635==    indirectly lost: 427,264 bytes in 1,075 blocks
==2635==      possibly lost: 243,262 bytes in 2,080 blocks

Re: [wxlua-users] Memory leak on checking for non-existing fields

[Paul K <pau...@ya...>]

Hi John,

Any update on a fix for this leak? It's easy to reproduce and would be
great if this could be fixed, but I can't figure out what resources
are not being collected...

One more detail on this; it appears to leak even on `ctrl[{}]` call,
which is the shortest branch of all the checks in
`wxlua_wxLuaBindClass__index` method. There is not much going on
before wxlua_error call, but since it's leaking on some other errors
too (for example, on wrong attribute types), I suspect it has
something to do with the error handling. I also tested with both Lua
5.1 and LuaJIT and the results are the same, so it seems like it's
wxlua-related.

Paul.

On Thu, Sep 3, 2015 at 9:13 AM, Paul K <pau...@ya...> wrote:
> Hi John,
>
> I noticed that there is a memory leak when wxlua script checks for
> non-existing properties inside pcall. For example, the following
> script leaks about 5M of memory on Windows:
>
> require "wx"
> local ctrl = wx.wxTextCtrl()
> for _ = 1, 10000 do pcall(function() return ctrl.foo end) end
> io.read()
>
> (if you are checking in TaskManager, you need to look for Lua process
> under "background processes" section).
>
> Adding "collectgarbage" doesn't help, so the leak seems to be in the
> memory allocated outside of Lua.
> "pcall" is needed to avoid "wxLua: Unable to call an unknown method
> 'foo' on a 'wxTextCtrl' type." If the check is for the existing
> property, then there is no leak. If I cause the error in "pcall" in
> some other way, there is no leak either. I don't think pcall is
> causing the issue; there is probably something wrong with the cleanup
> after the error.
>
> Do you have any idea on what may be causing this? I wouldn't worry
> about it too much, but there is no way to check if the property exists
> without wrapping the check into a "pcall" and leaking 0.5k per check
> is a bit too much.
>
> As a side note, I'd prefer "obj.foo" check to return "nil" instead of
> failing with an error. This would be a behavior consistent with how
> fields behave for tables in Lua.
>
> Paul.

[wxlua-users] Running a .wx.lua.....

[Hernan C. <jhe...@gm...>]

confirm 2d3d812c0ac3bb262df0416eda96a24521da9475
Hello, friends.

I am initiating in wxLua, that is Lua with Widgets.

I can run a .lua with lua51 and lua53. I am interested in Lua53.

I can run a .wx.lua with lua51, but not with lua53, but I am interested in
lua53.

Can you tell me how can I run the wxLua examples in lua v5.3?

Thank you.

*HERNAN CANO M.*
Systems Analyst - Programmer

Re: [wxlua-users] wxStyledTextCtrl:AppendText

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

On Fri, Oct 23, 2015 at 3:55 AM, Victor Bombi <so...@te...> wrote:

> try it without "\n" (all in a line)
>

I'm guessing that's a limitation of the number of columns Scintilla
handles, it looks like one bit less than a 2-byte short. Maybe the last
bit/values are used for some metadata. I don't see any recent Scintilla
documentation about limitations, but I wouldn't be surprised.

Here's some older limitations:
http://scintilla-interest.narkive.com/Ciq49QLW/long-lines

Regards,
    John




> ----- Original Message -----
> *From:* John Labenski <jla...@gm...>
> *To:* wxl...@li...
> *Sent:* Friday, October 23, 2015 5:42 AM
> *Subject:* Re: [wxlua-users] wxStyledTextCtrl:AppendText
>
>
> On Sun, Oct 18, 2015 at 2:27 PM, Victor Bombi <so...@te...>
> wrote:
>
>> Hi,
>>
>> 32*1024 - 7 is the maximum string len that is displayed in
>> wxStyledTextCtrl
>> with AppendText.
>> I have not seen anywhere information related.
>> Is this information in any place?
>> Is there any way to get a longer display length?
>>
>>
> Maybe there is an invalid utf8 char at that position that truncates it?
>
> I added this line to the end of the samples/editor.wx.lua LoadFile
> function and got all 40000 lines and even tried a larger value without a
> problem.
>
> function LoadFile(filePath, editor, file_must_exist)
> ...
>     editor:AppendText(string.rep("1234567890\n", 40000))
>     return editor
> end
>
> Regards,
>     John
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
>
> ------------------------------
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>

Re: [wxlua-users] wxLua x64

[Björn K. <ter...@cy...>]

Hi,

even if this is not directly wxLua related: i can give a confirmation 
for that "long/size_t" problem on 64bit windows8+ and that today this 
thread gave me the correct kick in the right direction for another 
project. Thank you very much!

Since some days i had a problem getting a lua/ffi 64bit project running 
on windows8. It seems that some ASLR magic is done since windows8 which 
causes some problems. I tried "unsigned long long" before but it didn't 
work here. I am not sure if there was another problem too, i have to 
check that again.

Bye
Björn



On 23.10.2015 09:56, Laurent Renoux wrote:
> Thx for your answer.
>
> Sorry for my approximation, I only work under Windows. I use Visual 2012
> where size_t is defined as follow
>
> #ifndef_SIZE_T_DEFINED
>
> #ifdef_WIN64
>
> typedefunsigned__int64size_t;
>
> #else
>
> typedef_W64 unsignedintsize_t;
>
> #endif
>
> #define_SIZE_T_DEFINED
>
> #endif
>
> In x64
>
> sizeof(long) = 4
>
> sizeof(long long) = 8
>
> sizeof(size_t) = 8
>
> In x86
>
> sizeof(long) = 4
>
> sizeof(long long) = 4
>
> sizeof(size_t) = 4
>
> Regards,
>
> Laurent
>
> *De :*John Labenski [mailto:jla...@gm...]
> *Envoyé :* vendredi 23 octobre 2015 05:13
> *À :* wxl...@li...
> *Objet :* Re: [wxlua-users] wxLua x64
>
> On Thu, Sep 3, 2015 at 8:03 AM, Laurent Renoux <lr...@iv...
> <mailto:lr...@iv...>> wrote:
>
>     Hi John,
>
>     At first, i would like to tell you how big is your works : thanks
>     for all.
>
>     I use wxLua with wxWidget 3.0.2 since 1 year on x86 and x64
>     platforms on Windows 7 with no matter. Since I have jumped on
>     Windows 10, wxLua crash on x64. Same dll, same code. I think, I have
>     found the problem.
>
>     In file wxlstate.cpp In function
>
>     void* LUACALL wxluaT_getuserdatatype(lua_State* L, intstack_idx,
>     intwxl_type)
>
>                   long int o = (long int)wxlua_touserdata(L, stack_idx,
>     false);
>
>     should be changed in
>
>                   size_t o = (size_t)wxlua_touserdata(L, stack_idx, false);
>
>     on Windows platforms to avoid original pointer to be truncated in 32
>     bits. Why it doesn’t crash since 1 year on Win7, I really don’t
>     know, probably I’m a lucky man and memory management has changed on
>     Win10 !
>
> Humm, my understanding was that both long and size_t are 4 bytes on a
> 32-bit architecture and 8 bytes on a 64-bit architecture, but I see now
> that there are claims that Visual Studio kept long at 4 bytes on x64. It
> seems like there is no guarantees about size_t other than that it will
> be unsigned in the C++ standard.
>
> Can you please print sizeof(long) and sizeof(size_t) and let me know
> what compiler you use?
>
>
> I should use an uintptr_t, but older Visual Studio versions don't have
> inttypes.h so I've changed it to 'unsigned long long' so it'll work
> everywhere. The change is committed to svn.
>
> Regards,
>
>       John
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>

Re: [wxlua-users] wxLua x64

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

On Fri, Oct 23, 2015 at 3:56 AM, Laurent Renoux <lr...@iv...>
wrote:

> Thx for your answer.
>
>
>
> Sorry for my approximation, I only work under Windows. I use Visual 2012
> where size_t is defined as follow
>
>
Ok, thanks. Let me know if 'unsigned long long' doesn't work. It's
suboptimal for 32-bit, but I think compiler compatibility trumps that.
Someday I'll move the code into the 21st century.

Thanks,
    John



>
>
>
>
> #ifndef _SIZE_T_DEFINED
>
> #ifdef  _WIN64
>
> typedef unsigned __int64    size_t;
>
> #else
>
> typedef _W64 unsigned int   size_t;
>
> #endif
>
> #define _SIZE_T_DEFINED
>
> #endif
>
>
>
> In x64
>
>
>
> sizeof(long) = 4
>
> sizeof(long long) = 8
>
> sizeof(size_t) = 8
>
>
>
> In x86
>
>
>
> sizeof(long) = 4
>
> sizeof(long long) = 4
>
> sizeof(size_t) = 4
>
>
>
>
>
> Regards,
>
>
>
> Laurent
>
>
>
>
>
> *De :* John Labenski [mailto:jla...@gm...]
> *Envoyé :* vendredi 23 octobre 2015 05:13
> *À :* wxl...@li...
> *Objet :* Re: [wxlua-users] wxLua x64
>
>
>
> On Thu, Sep 3, 2015 at 8:03 AM, Laurent Renoux <lr...@iv...>
> wrote:
>
> Hi John,
>
>
>
> At first, i would like to tell you how big is your works : thanks for all.
>
>
>
> I use wxLua with wxWidget 3.0.2 since 1 year on x86 and x64 platforms on
> Windows 7 with no matter. Since I have jumped on Windows 10, wxLua crash on
> x64. Same dll, same code. I think, I have found the problem.
>
>
>
> In file wxlstate.cpp In function
>
>
>
> void* LUACALL wxluaT_getuserdatatype(lua_State* L, int stack_idx, int
> wxl_type)
>
>
>
>              long int o = (long int)wxlua_touserdata(L, stack_idx, false);
>
>
>
> should be changed in
>
>
>
>              size_t o = (size_t)wxlua_touserdata(L, stack_idx, false);
>
>
>
> on Windows platforms to avoid original pointer to be truncated in 32 bits.
> Why it doesn’t crash since 1 year on Win7, I really don’t know, probably
> I’m a lucky man and memory management has changed on Win10 !
>
>
>
>
>
> Humm, my understanding was that both long and size_t are 4 bytes on a
> 32-bit architecture and 8 bytes on a 64-bit architecture, but I see now
> that there are claims that Visual Studio kept long at 4 bytes on x64. It
> seems like there is no guarantees about size_t other than that it will be
> unsigned in the C++ standard.
>
> Can you please print sizeof(long) and sizeof(size_t) and let me know what
> compiler you use?
>
>
> I should use an uintptr_t, but older Visual Studio versions don't have
> inttypes.h so I've changed it to 'unsigned long long' so it'll work
> everywhere. The change is committed to svn.
>
> Regards,
>
>      John
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> wxlua-users mailing list
> wxl...@li...
> https://lists.sourceforge.net/lists/listinfo/wxlua-users
>
>

Re: [wxlua-users] wxLua x64

[Laurent R. <lr...@iv...>]

Thx for your answer.

Sorry for my approximation, I only work under Windows. I use Visual 2012 where size_t is defined as follow


#ifndef _SIZE_T_DEFINED
#ifdef  _WIN64
typedef unsigned __int64    size_t;
#else
typedef _W64 unsigned int   size_t;
#endif
#define _SIZE_T_DEFINED
#endif

In x64

sizeof(long) = 4
sizeof(long long) = 8
sizeof(size_t) = 8

In x86

sizeof(long) = 4
sizeof(long long) = 4
sizeof(size_t) = 4


Regards,

Laurent


De : John Labenski [mailto:jla...@gm...]
Envoyé : vendredi 23 octobre 2015 05:13
À : wxl...@li...
Objet : Re: [wxlua-users] wxLua x64

On Thu, Sep 3, 2015 at 8:03 AM, Laurent Renoux <lr...@iv...<mailto:lr...@iv...>> wrote:
Hi John,

At first, i would like to tell you how big is your works : thanks for all.

I use wxLua with wxWidget 3.0.2 since 1 year on x86 and x64 platforms on Windows 7 with no matter. Since I have jumped on Windows 10, wxLua crash on x64. Same dll, same code. I think, I have found the problem.

In file wxlstate.cpp In function

void* LUACALL wxluaT_getuserdatatype(lua_State* L, int stack_idx, int wxl_type)

             long int o = (long int)wxlua_touserdata(L, stack_idx, false);

should be changed in

             size_t o = (size_t)wxlua_touserdata(L, stack_idx, false);

on Windows platforms to avoid original pointer to be truncated in 32 bits. Why it doesn’t crash since 1 year on Win7, I really don’t know, probably I’m a lucky man and memory management has changed on Win10 !


Humm, my understanding was that both long and size_t are 4 bytes on a 32-bit architecture and 8 bytes on a 64-bit architecture, but I see now that there are claims that Visual Studio kept long at 4 bytes on x64. It seems like there is no guarantees about size_t other than that it will be unsigned in the C++ standard.
Can you please print sizeof(long) and sizeof(size_t) and let me know what compiler you use?

I should use an uintptr_t, but older Visual Studio versions don't have inttypes.h so I've changed it to 'unsigned long long' so it'll work everywhere. The change is committed to svn.
Regards,
     John

Re: [wxlua-users] wxStyledTextCtrl:AppendText

[Victor B. <so...@te...>]

try it without "\n" (all in a line)
  ----- Original Message ----- 
  From: John Labenski 
  To: wxl...@li... 
  Sent: Friday, October 23, 2015 5:42 AM
  Subject: Re: [wxlua-users] wxStyledTextCtrl:AppendText




  On Sun, Oct 18, 2015 at 2:27 PM, Victor Bombi <so...@te...> wrote:

    Hi,

    32*1024 - 7 is the maximum string len that is displayed in wxStyledTextCtrl
    with AppendText.
    I have not seen anywhere information related.
    Is this information in any place?
    Is there any way to get a longer display length?




  Maybe there is an invalid utf8 char at that position that truncates it?


  I added this line to the end of the samples/editor.wx.lua LoadFile function and got all 40000 lines and even tried a larger value without a problem.

  function LoadFile(filePath, editor, file_must_exist)
  ...

      editor:AppendText(string.rep("1234567890\n", 40000))
      return editor
  end


  Regards,

      John




------------------------------------------------------------------------------


  ------------------------------------------------------------------------------



------------------------------------------------------------------------------


  _______________________________________________
  wxlua-users mailing list
  wxl...@li...
  https://lists.sourceforge.net/lists/listinfo/wxlua-users

Re: [wxlua-users] Add methods for wxwidgets 3.x (was: How to provide wxApp::MacNewFile, wxApp::MacOpenFiles, and wxApp:MacReopenApp methods?)

[Paul K <pau...@ya...>]

Hi John,

> These will require a C++ wxLuaApp class that have its virtual functions called by wxWidgets and then forward them to an overridden Lua function if supplied, similar to how printing is implemented.

That's a good lead; I'll take a look at that.

> Sorry, I don't know. To be sure, these are basically drag and drop handlers?

Mostly, except probably MacAppReopen. I think they all have the same
structure with C++ callback function called, which then calls a Lua
function (if setup).

Paul.

On Thu, Oct 22, 2015 at 8:52 PM, John Labenski <jla...@gm...> wrote:
> On Wed, Oct 21, 2015 at 5:52 PM, Paul K <pau...@ya...> wrote:
>>
>> Hi John,
>>
>> > I'm still in need of having MacNewFile, MacOpenFiles, and MacReopenApp
>> > methods (http://docs.wxwidgets.org/trunk/classwx_app.html) and would
>> > appreciate any update on when you may have chance to add them.
>>
>> Do you have any update on Mac* methods or any suggestion on how these
>> can be added? Maybe you can do one or two of them and I'll use it as
>> an example to complete the other methods? It would be good to also add
>> MacPrintFile and MacOpenURL as my product now supports file printing
>> as well.
>>
>
> These will require a C++ wxLuaApp class that have its virtual functions
> called by wxWidgets and then forward them to an overridden Lua function if
> supplied, similar to how printing is implemented.
>
> The problem is that I don't have a Mac so I can't test and this not the sort
> of code that can be blindly written with any hope of it working or even
> compiling.
>
>>
>> If you are not available to work on this, can you recommend someone
>> who can do this or at least to provide some initial implementation.
>> Thank you.
>>
>
> Sorry, I don't know. To be sure, these are basically drag and drop handlers?
>
> Regards,
>     John
>
>
>> On Sat, Feb 21, 2015 at 2:52 PM, Paul K <pau...@ya...> wrote:
>> > Hi John,
>> >
>> > I'm still in need of having MacNewFile, MacOpenFiles, and MacReopenApp
>> > methods (http://docs.wxwidgets.org/trunk/classwx_app.html) and would
>> > appreciate any update on when you may have chance to add them.
>> >
>> > If you don't have time at all to work on these and other methods, could
>> > you
>> > give me a hint on how these can be added or maybe implement one of them
>> > and
>> > I'll take care of the others? I can add existing methods (like those
>> > needed
>> > for wxSTC or wxTreeCtrl), but it seems like these methods need some sort
>> > of
>> > callback and I don't know how to provide that.
>> >
>> > Paul.
>> >
>> >
>> > On Thu, Oct 30, 2014 at 11:01 AM, Paul K <pau...@ya...> wrote:
>> >>
>> >> Hi John,
>> >>
>> >> >> > I'm looking for a way to provide MacNewFile, MacOpenFiles, and
>> >> >> > MacReopenApp methods
>> >> >> > (http://docs.wxwidgets.org/trunk/classwx_app.html), but can't
>> >> >> > figure
>> >> >> > out how to do this in wxlua and don't see this in any of the
>> >> >> > examples.
>> >> >>
>> >> >> Can these methods be used with the current version of wxlua or do
>> >> >> they
>> >> >> need to be added first?
>> >> >
>> >> > They need to be added, it should be doable.
>> >>
>> >> Any plans to add these methods?
>> >>
>> >> Also, I have a short list of various methods that exist in wxwidgets
>> >> 3.x, but are missing from wxlua API:
>> >>
>> >> wxTopLevelWindow needs EnableFullScreenView
>> >> wxTreeCtrl needs GetFocusedItem, SetFocusedItem, ClearFocusedItem
>> >> wxSTC needs ScrollRange, ScrollCaret, SetFontQuality, AddStyledText
>> >> wxAuiTabArt needs SetColour and SetActiveColour
>> >>
>> >> If it makes things easier for you, I can probably submit the initial
>> >> patch that adds these methods, but AddStyledText seems to be disabled
>> >> explicitly, so I'd appreciate if you could check why that's the case.
>> >> Thank you.
>> >>
>> >> Also, it's possible to provide my own wxAuiTabArt provider?
>> >>
>> >> Paul.
>> >
>> >
>
>