try...catch (Error handling)

http://lua-users.org...1/msg00650.html

Although this is for c++ its basically self explanatory and I would love to see this in the next update.

It's another suggestion that can be implemented client side with the tools already available to you.

KleptoKat, on 05 April 2013 - 04:55 PM said:

-snip-

Where is the code? I cannot see it in that link.

Cranium, on 05 April 2013 - 05:21 PM said:

It's another suggestion that can be implemented client side with the tools already available to you.

Oh, really? I'll look into that further, then..
With a little more research, I've come up with this that I did not know was their previously: (Feel free to lock this topic.)


pcall (f, arg1, ···)
[indent=1]
Calls function f with the given arguments in protected mode. This means that any error inside f is not propagated; instead, pcall catches the error and returns a status code. Its first result is the status code (a boolean), which is true if the call succeeds without errors. In such case, pcall also returns all results from the call, after this first result. In case of any error, pcall returns false plus the error message.[/indent]

Cranium, on 05 April 2013 - 05:21 PM said:

It's another suggestion that can be implemented client side with the tools already available to you.

Not to sound argumentative, but actually I don't believe it can be implemented with the tools available to us: not in that form anyway. If you take a look at the follow-up post, it's written in C as an extension for Lua.

But anyway, pcall does indeed do the same thing essentially.

Bubba, on 05 April 2013 - 09:13 PM said:

pcall does indeed do the same thing essentially.

Just an annoying way about it. Since if you have multiple statements you want to pcall, you have to check for an error after each pcall as opposed to a try catch you define the catch once and then can try heaps of statements…

Oh sure. Let me just rewrite LuaJ's error handling because you don't know how to use pcall.

theoriginalbit, on 05 April 2013 - 09:49 PM said:

Bubba, on 05 April 2013 - 09:13 PM said:

pcall does indeed do the same thing essentially.

Just an annoying way about it. Since if you have multiple statements you want to pcall, you have to check for an error after each pcall as opposed to a try catch you define the catch once and then can try heaps of statements…

You can capture lots of statements with pcall…

If you have multiple statements to sourround with try/catch, put them in a closure. thanks to upvalues, you don't even have to declare argument.

And I don't think they would event try to change the lua language just for you. They won't even use lua 5.2, which is ready here.

Lua 5.2 is a compatibility breaking update.

As in, "Lyqyd will no longer be compatible with the Ask a Pro section if everyone can use goto." ;)/>