📃 SLua Alpha

Listener doesn't work after the first message: local function listening(channel, name, id, msg) print(msg) end LLEvents:on("listen", listening) ll.Listen(1, "", "", "") [ typing: /1 hello] -- > hello [ typing: /1 hello] ( nothing ) --- Both listeners don't work after the first message to any of them local function listening(channel, name, id, msg) print(msg) end LLEvents:on("listen", listening) ll.Listen(1, "", "", "") ll.Listen(2, "", "", "") [ typing: /2 hello] -- > hello [ typing: /1 hello] ( nothing ) --- Event handlers are in place: local function listening(channel, name, id, msg) print(msg) end local function touching(events) for _, eventName in LLEvents:eventNames() do for _, myHandler in LLEvents:listeners(eventName) do print(`{eventName} : {debug.info(myHandler,"n")}`) end end end LLEvents:on("listen", listening) LLEvents:on("touch_start", touching) ll.Listen(1, "", "", "") [ typing: /1 hello] -- > hello [ touching ] -- > touch_start : touching -- > listen : listening [ typing: /1 hello] ( nothing ) --- This doesn't work, listeners are removed after calling the event handler: local function listening(channel, name, id, msg) print(msg) ll.Listen(1, "", "", "") end LLEvents:on("listen", listening) ll.Listen(1, "", "", "") --- This works: local function listening(channel, name, id, msg) print(msg) LLTimers:once(0.1, function() ll.Listen(1, "", "", "") ll.Listen(2, "", "", "") end) end LLEvents:on("listen", listening) ll.Listen(1, "", "", "") ll.Listen(2, "", "", "")

For instance: local greet = "Hello World" ll.Say(0, greet:gsub("World", "SecondLife")) --> Script run-time error: invalid argument #2 to 'Say' (Different number of arguments than expected) Because string:gsub() returns the resulting string and the number of substitutions. But: function say(msg) ll.Say(0, msg) end local greet = "Hello World" say(greet:gsub("World", "SecondLife")) -- > Hello SecondLife SLua functions discard extra parameters. Of course we can adjust the return: local greet = "Hello World" ll.Say(0, (greet:gsub("World", "SecondLife"))) -- > Hello SecondLife But discarding extra parameters would be a more Lua behaviour.

The LSL variables TRUE and FALSE both work as true in SLua. I'd suggest that rather than auto-define them, they should be left undefined. If not, a not uncommon error will be to type TRUE or FALSE when one meant true or false. Failing that, I'd suggest defining TRUE -> true and FALSE -> false. Thanks!

There has already been some discussion of this in other canny's Like here But a centralized issue for feedback is probably a better idea. As the post by Harold Linden says in the above link, LL are considering something like LLEvents.touch_start = function ... Personally I would rather suggest something more akin to local handle = llevent.onTouchStart(function(touches:number) end) local handle = llevent.dispose(handle) or local handle = llevent.on(llevent.TOUCH_START, function(touches:number) end) llevent.dispose(handle) or (nya's suggestion) local function touchHandler(touches: number) end llevent.on(llevent.TOUCH_START, touchHandler) llevent.off(llevent.TOUCH_START, touchHandler) Mostly to allow for if not now, at least in the future multiple event handlers being setup and expanding to support things similar too function listenHandler(channel, name, key, msg) end local listener = ll.Listen(0,"","","test") llevent.on(llevent.LISTEN, listenHandler, listener) or function listenHandler(channel, name, key, msg) end llevent.on(llevent.LISTEN, listenHandler, {channel=0,message="test"}) Possibly something similar to roblox's "standard" , or something designed in a way that is compatible with it, so it can be properly extended later. This needs to happen BEFORE a possible beta phase There should also be NO COMPATABILITY with the current way of working, all current scripts SHOULD break and need rewriting, having both is not really a good option, and NOW is the time for breaking that.

Common usage of methods like ll.AgentInExperience etc in lsl is to just stick them in an if directly as 1 evaluates true As this is not the case in lua, it would be good for the relevant functions to return booleans. I have scoured the function list and updated the wiki to include all the ones I could see on a first pass through. https://wiki.secondlife.com/wiki/Category:LSL_Functions/Returns_a_integer/boolean ll.AgentInExperience ll.DerezObject ll.EdgeOfWorld ll.GetScriptState ll.GetStatus ll.IsFriend ll.ManageEstateAccess ll.SameGroup ll.ScaleByFactor ll.ScriptDanger ll.SetMemoryLimit Were missing and I added them, listed separately in case they are "wrong" ll.DetectedGroup ll.IsLinkGLTFMaterial ll.OverMyLand ll.SetRegionPos ll.VerifyRSA

Currently, when scripting in Luau, indexing of tables does not match between Luau functions and ll. functions. For example, the following return the same values: str = ll.List2String(List,2) and str = List[3] This isn't exactly a bug, both are functioning 'correctly', but it's going to cause some issues. Is there a reasonable solution to this?

Second Life Project Lua Editor 7.1.12.14888088240 (64bit) I created a short script demonstrating multiple inheritance in SLua. The program worked exactly as intended until I added a call to ll.SetText at the beginning of the script, whereupon the script produced an incomprehensible "Failed to perform mandatory yield" error when the __index function was invoked. Attached is a stripped down version of the script demonstrating the problem, together with various commented out alternatives trying to narrow the problem down. Details of trying the alternatives, and the full error message are included in the comments at the end of the script.

--ll.Dialog(ll.GetOwner(), "Empty Table", {}, 1) --This works, presents the dialog and prints done. ll.Dialog(ll.GetOwner(), "Nil", nil, 1) --This hangs, no dialog, no done. Should either trigger an error or treat nil as an empty table. print("done") You can thank a puzzled SLua class student, Marie (MarieOmani), for triggering this error.

In LSL, functions like llGetTexture() return either a texture name or its UUID, both as strings, and string–key comparisons work. In SLua, string and uuid are distinct types. For instance, in an object with blank textures: print( ll.GetTexture(0) == TEXTURE_BLANK ) -- > false We must cast to uuid: print( uuid( ll.GetTexture(0) ) == TEXTURE_BLANK ) -- > true

This was briefly discussed in the original table to json feature . It would be useful to have to allow for encoding of more complex data structures, also to allow tables that have functions to be encoded by specifying them to not be included Probably best for __tojson to return what we want to be encoded rather than actual json? local Nested = {} Nested.__index = Nested function Nested:__tojson() return { name= self.name, child= if self.child then self.child else nil } end function Nested.new(name,parent) return setmetatable({ name=name, parent=parent, child=nil },Nested) end local root = Nested.new("root") root.child = Nested.new("child1",root) root.child.child = Nested.new("child2",root.child) ll.OwnerSay(lljson.encode(root)) Possibly this is deemed too much of an addition as it can be achieved atm with this local Nested = {} Nested.__index = Nested function Nested:__tojson() return { name= self.name, child= if self.child then self.child:__tojson() else nil } end function Nested.new(name,parent) return setmetatable({ name=name, parent=parent, child=nil },Nested) end local root = Nested.new("root") root.child = Nested.new("child1",root) root.child.child = Nested.new("child2",root.child) ll.OwnerSay(lljson.encode(root:__tojson()))