Best way to handle a nil object...pcall or LUA module/table?

[schlista]

Ok so I have two methods that work for handling a nil object.

One is to use a pcall and trap the error and I know the issue is the object doesn’t exist.

The other is to track all objects via a LUA module and then confirm if the object exists before calling it.

I know relying on errors isn’t clean code, but performance speaking which will give better results? Let’s say I have around 200 objects to track at most. Is it better to keep checking if it exists? Or just assume it does then give an error if it doesn’t (which is trapped with pcall…so I know it no longer exists).

[britzl]

@schlista

Ok so I have two methods that work for handling a nil object.

One is to use a pcall and trap the error and I know the issue is the object doesn’t exist.

The other is to track all objects via a LUA module and then confirm if the object exists before calling it.

There is also go.exists(id) created specifically to check if a game object still exists.

[schlista]

Oh wow. I missed that. That should be perfect. Thank you.