(lua+) argh this is driving me nuts

[xyzzy]

so anyway, i've been working on a lua script which i have recently attempted to convert from the first lua object (which i'll call: lua') to lua+ (because of the HWA problems i pointed out with the former). however, i've been having a problem with lua+, which is shown in the app in this link: scripts and app
i downloaded the updated lua+ from this topic prior to converting this script

anyway, that app has two frames, one for lua' and one for lua+. The lua' frame SHOULD work for you; it'll have 5 bouncing balls if it does. The lua+ frame, on the other hand, will likely flood the listbox with a "Could not call Lua function "OBJECTSYSTEM"" error.

Both scripts included are exactly the same, barring the function formatting differences needed for the objects. From what i've experimented with in regards to the lua+ side, it looks like the MP_TEST function is not able to access the me table for some reason, while it can in the lua' side. Commenting out the Obj:MP_TEST part in the OBJECTSYSTEM function of the lua+ script will cease the errors. Leaving it as it is and uncommenting the me = { blahblah } part in the MP_TEST function will also cause the errors to stop (but the objects won't be at 0,0 like they should be)

i am by no means an expert in lua, and for all i know i'm exploiting a bug in the lua' object, but unless i screwed up badly in either the script or the MMF code, i can't imagine why this would work in one object but not the other

[Retriever2]

From what I could see, you were pushing the last few arguments of your CreateObject function as strings, but using them later on as numeric values in arithmetic instead, which creates a cascading error that gets returned as that really, really ambiguous error.

Edit: It's more subtle than that, they can deal with valid numeric string representations, but with the lua+ frame you were passing empty strings, and with lua', you were passing numeric strings.

[xyzzy]

haha i feel stupid now

i thought lua would automatically convert variable types (technically they're supposed to be strings but in this case i was using them as placeholder values)

anyway this topic can be locked/ignored/whatever now

[James]

I'm glad you figured it out I am working on some better error reporting for the next version.