John Labenski writes:
I do not think it would effect any existing programs since they did not expect
any parameters to the function.
I use wxluafreeze with some of my programs and it had no side effects since
I never used ... in any of these programs.
Andre
---
On Mon, Aug 23, 2010 at 9:39 PM, AndreArpin wrote:
> AndreArpin writes:
>
>> The following changes allow Lua programs to use the ... construct instead of
>> using the obsolete arg variable.
I see that that the Lua 5.1.4 (the current Lua) that wxLua uses pushes
the global table "arg" in wxLua/mod
AndreArpin writes:
>
> The following changes allow Lua programs to use the ... construct instead of
> using the obsolete arg variable.
>
int wxLuaState::RunFile(const wxString &filename, int nresults)
{
lua_State* L = M_WXLSTATEDATA->m_lua_State;
wxCHECK_MSG(Ok(), LUA_ERRRUN, wxT("
AndreArpin writes:
>
> The following changes allow Lua programs to use the ... construct instead of
> using the obsolete arg variable.
>
The proposed change do not imitate the lua code I will have to think about it.
I
have been to hasty.
Andre
-
AndreArpin writes:
> The following change increase the compatibility between wxlua and lua
> ...
I also remove arg[0] which is the path of the current running program which is
not good.
So I renege on this one.
Andre
The following changes allow Lua programs to use the ... construct instead of
using the obsolete arg variable.
vg:
given the program test.lua
print(#arg)
print(#...)
wxlua -c -r test.lua 1 2 3
will produce
3
3
instead of an error
int wxLuaState::RunFile(const wxString &filename, int nresults)
{
