Override Mushclient's luasocket

Hello,

I am trying to get a mushclient world to load luasocket 2.0.2 instead of Mushclient's built in 2.0.1 because of a certain memory bug in 2.0.1.

I placed the socket.lua in my world's directory, along with the socket folder containing all the sub libraries and the core.dll. Before the requires in my script, I do a ChangeDir(GetInfo(67)) to make my world's directory the current directory.

It correctly loads socket.lua from the world directory, but then loads Mushclient's core.dll, even though it is supposedly lower priority than loading from current directory. When I delete Mushclient's core.dll, it correctly loads the one in my world's socket folder, but while Mushclient's files are in place there seems to be no way to get it to load mine first. It's already higher priority in package.path, so it doesn't look like I can get anywhere by manipulating that.

Here is my package.path



Here is my package.cpath



And here is a traceback for doing a require "socket.x" (the real command is require "socket.core")



Everything seems to say it should load from the socket folder in the current directory first, but this is not the case. Is there anything I can do to work around this without changing Mushclient's files? Alternatively, officially upgrading Mushclient's luasocket to 2.0.2 would be great too. :)

I'm not sure what you mean by Mushclient's core.dll.

There are (confusingly) two core.dll files supplied with LuaSocket. One goes into the mime subdirectory and one into the socket subdirectory. If you replace both of them with the correct ones from the download, and replace all the .lua files with the ones of the same name from the download, it should work. It did for me.

Anyway, version 4.81 will have LuaSocket 2.0.2 as you suggested.

Wow, I didn't even notice there was a second core. Still, it doesn't seem to help any. If you mean replace Mush's .lua files and dll's, then yes that does work. What I was trying to do though was make it load a copy of luasocket from the world's directory instead from mushclient's. That way I could deploy the world on other computers without any assumptions about their installation. This didn't work because somehow it was defying the package.path ordering, but if 4.81 will have it, then I'm not going to lose any sleep over it.