📃 SLua Alpha

Externally edited files currently go to strange locations and have strange names. If this could be normalized a bit, it would make it easier to use Git or similar code managers to keep versioned copies of one's scripts. As things stand now, one typically has to make a copy of the script, give it a standard name and then save to the local repo folder, then version it. I'm hoping something better can be devised.

I'd like to suggest including scripting school regions in the SLua beta testing on the main grid. These regions could offer a useful testing environment, with motivated students and instructors who would be glad to provide feedback. I mentioned this at the August 5th SUG meeting: [12:18] Suzanna (suzannalinn): Will the regions with scripting schools be able to get SLua Beta? [12:19] Rider Linden: That's a pretty good idea Suzanna. Would you put something on the SLua board in Canny to remind me about that when we start selecting regions? Allowing schools to teach SLua on the main grid would greatly benefit students: No need to switch grids or recreate inventories. More accessible and comfortable learning environment. Better attendance and continuity. Easier integration into existing classes. More realistic feedback from live educational use. Thanks for considering this!

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!

For example: t = {} t[10] = true print(lljson.encode(t)) returns: [null,null,null,null,null,null,null,null,null,true] But: t = {} t[11] = true print(lljson.encode(t)) throws the error: Cannot serialise table: excessively sparse array It could instead be encoded as an object. Or always encoded as an object when #t == 0 or next(t, #t) ~= nil .

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 to get the magnitude of a vector v we might code local v = vector(1,2,3) local m = vector.magnitude(v) One might reasonably expect local m = v:magnitde() to work, and similarly for other functions that might reasonably act like methods such as local dp = v1:dot(v2) and so on. It does not work because a vector instance's metatable is not set to the functions in vector . Seems to me that it should be, so that vectors can be treated like any other SLua object or smart table. I was somewhat surprised to find that vector is implemented as a native type rather than as an ordinary Lua table / object, with the functions in its metatable and so on. I would suppose that this might be because Luau already did it this way, or because of some performance concern. Curious. In any case, since, in my view, any competent Lua / SLua scripter is going to use objects and the : notation, vectors (and quaternions and any other built-in structured types) would be far better if they worked like objects with metatables. Thank you for your consideration and I'll be happy to assist with testing or Lua code if it would be useful.

function touch_start(total_number) ll.Say(0, "Touched.") end ll.OwnerSay("Hello, Avatar!") It's confusing for LSL scripters who are starting to learn SLua to be told that state_entry() doesn't exist, when the sample script includes it. There are many "Hello, Avatar!" messages in scripting classes or sandboxes.

Incorporate a SLua sub forum into the SL forums. The LSL Scripting section has been invaluable to many over the years and a new section would be as well.