XLua, MMF2 Extension

_G is the global table. It's like any other table in Lua but it has all the global functions/variables/etc.

can't really seem to get anything out of it, I tried

for index, value in ipairs(_G) do print(value) end

and it didn't print anything. Any ideas that might help me?

You have to use pairs, not ipairs. ipairs will only enumerate consecutive integer indices.

for index, value in pairs(_G) do print(index, value) end

This post has been edited by Retriever II on Aug 7 2009, 03:13 PM

Thank you. But is there any way to retrieve the name of the function? It only returns id.

This post has been edited by Mecha the Slag on Aug 7 2009, 03:15 PM

Run the code I posted, it prints index (name) and value

I don't see any foo ):

thats... not what I'm getting at all. Can you send me the mfa you're using?

http://hocuspocus.taloncrossing.com/rii/interpreter.mfa

Oh... I forgot to turn on the vertical scrollbar

cheers

I figured out your problem.

Notice how the error is referencing DoCall instead of the actual registered function. Every registered function is translated like so:

So when you have a triggered error on parameter a, even though it's at index 1, it's actually at index 2 of DoCall.

What actually is triggering your error in the first place is trying to pass a function or a table as a parameter. Mystery dispelled!

Obviously this situation could use some improvement.

Also CALLOUT TO XGOFF: You mentioned a couple pages back about the lua demo giving better error feedback than XLua. Do you have a concrete example of what it's returning that you like?

alright cheers

Would it be possible to add a "on new function registered"? Don't really need to know anything on the new function, I just need to know when I need to update my list of functions.

This post has been edited by Mecha the Slag on Aug 8 2009, 02:28 AM

Sounds reasonable. There's already an OnExport callback so why not.

Also I'm doing some overhauling of error reporting for the next release. At minimum, all MMF-triggered errors should now list the event number where the error was trapped.

would it be possible to have a 'silence mode' of sort, which runs like normal, but all normally MMF registered functions are ignored. This will allow me to run my lua scripts without having to have the million of mmf registered functions I have, yet still be able to get returned errors.

So running the script like normal, without the side effect of it actually doing anything

edit: also sorry if I missed it but, does two xlua objects in same frame work?

This post has been edited by Mecha the Slag on Aug 8 2009, 04:32 PM

I'm really not sure what you're getting at with silent mode.

Yes, you can use 2 XLua objects. You can bind them to separate states, or you can even bind them to the same state although that doesn't really do anything for you.

Something I do plan on adding shortly is a way for states to communicate with each other (basically one state allows certain functions or tables to be accessed by another state). This way you could use a second state to effectively sandbox user scripts, exposing only your API and hiding all the MMF/WIN/io/registered functions/etc that your own scripts depend on. Such a solution presents a little more overhead however.

say I have a normal script with 2 registered mmf functions

in normal mode, xlua would call the "on functions" inside mmf2
if the functions aren't registered it'll produce an error

in silenced mode, xlua won't call the "on functions" inside mmf2
if the functions aren't registered it'll ignore it

There's not really any way to avoid generating an error when you call an invalid symbol (e.g. your unregistered function).

What are you ultimately trying to achieve.

checking for errors

well like any sort of syntax error

something like t = {1, 2, 3, 4 5, 6, 7} throws "input:1: '}' expected near '5'" in lua.exe but xlua just says "syntax error"

though that's an understated example it's quite annoying to get that in a 2000-line script, because notepad++ and probably other editors won't notice those types of syntax errors unlike missing brackets or 'end's... though i guess it's better than lua+'s behavior ie crashing

then there's stuff like the tracebacks:

i'd imagine there would be an option in xlua to enable/disable tracebacks because they'd probably get annoying sometimes

This post has been edited by Xgoff on Aug 9 2009, 11:11 PM

also how do you take advantage of states being global across frames

binding a second xlua (in a subapp frame) to state 0 (the one i'm using) doesn't seem to work