lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]


> > 	Thanks for the reply, and for that information; I had experienced
> > troubles using LuaSocket in 5.1 (I have reverted to 5.0 because of
> > that), and was hoping you may be working on an update for this!  I shall
> > wait until your next release to try it out then.
> That would be a good time to report problems... What kind of issue did
> you encounter? I was under the (wrong?) impression LuaSocket worked fine
> with 5.1.

	Sorry; because it happened right at the start, I assumed it must be an
obvious, common problem --- obviously not.  Here's what I get (Linux
2.6, LuaSocket 2.0-final):

$ ./lua
Lua 5.1  Copyright (C) 1994-2006, PUC-Rio
> socket = require("socket")
error loading module 'socket.core' from file './socket/':
        ./socket/ undefined symbol: lua_newtable
stack traceback:
        [C]: ?
        [C]: in function 'require'
        ./socket.lua:13: in main chunk
        [C]: in function 'require'
        stdin:1: in main chunk
        [C]: ?

	However, with the same system and LuaSocket compile:

$ lua
Lua 5.0.2  Copyright (C) 1994-2004 Tecgraf, PUC-Rio
> require("compat")
> socket = require("socket")
> = socket
table: 0x807c530

	The only differences are the Lua versions, and the use of compat in
5.0.2 --- if I use compat in 5.1 as well, then I get a `compat.lua:190:
attempt to call a string value' error, but I would not imagine I am
supposed to use compat here.

	-- Matthew