Issue with select() and IsInInstance()
 

Is there a reason why:


returns BOOLEAN, TYPE

and


returns BOOLEAN TYPE together? Select(2, *) returns JUST the type, so why can't I return just the boolean?

Because select returns all values after the one specified, as well.

If you just want the first value, just do "local inInstance = IsInInstance()".

There is a way to force it to only return one value, and that's by wrapping it in parentheses, but there's no reason to do that here.

Nevermind, thank you.

Zzzzz -.-

I would be instrested with this force only the selected value. Is this some kinda new bug, i think it only returned the actually selected parameter.

Normal lua behavior, use (IsInInstance()) to only get the first.

Well obv. i want to use it on a different stuff like "print(select(2, GetWorldStateUIInfo(3)))" prints every parameter from the second one.

You need to wrap your function in parenthesis like so:

print((select(2, GetWorldStateUIInfo(3))))

If that doesn't work, try:

local _, state = GetWorldStateUIInfo(3)

Edit: Fixed a mistake.

Oh i see, thanks. Yeah i dont really wanna go back for the _, method.

It's not a bug, it's even documented as doing such. See Select() under Official Lua 5.1 Manual §5.1.



As mentioned earlier, encase the Select() call in parenthesis to only use the first return.
(The post by Clamsoda put them around the wrong function.)

And i need to double wrap is its already wrapped like that?

"tostring(select(2, GetWorldStateUIInfo(3)))"

If you're doing something computationally expensive (such as an often-used loop or polling the combat log), you'll want to avoid using select() and use the placeholder "_" variable name.

Yes. You need to wrap select() in its own parenthisis, THEN wrap that in tostring() -- or whatever function you are calling -- if you want to JUST return the 2nd argument of GetWorldStateUIInfo().


There really is no downside to using the "local _, state = GetWorldStateUIInfo(3)" approach, especially when you are only one argument deep into the function. It is faster, and you can just make "_" local in your file if your are worried about global leaks (though that was fixed).

I don't really see why, since its still gonna overwrite _ variable all the time the event happens, and since you don't use it its just a waste of memory and processor time. And select only gets the parameters you'll need and use, but ofc calling the select itself is also uses resources.

Calling Select uses a lot more resources than redefining a variable. Only really important if being called a lot though.

Calling the select() function is extremely slow. Besides, you are just recycling "_" over and over. It is one variable, there isn't much overhead associated with that.

Select or not to select
 

So i shouldn't use select on "COMBAT_LOG_EVENT_UNFILTERED"?

oooh :( no.

On a related note, I saw this in an AddOn I downloaded a while back:
Would this not be the same as:

Yes. No offense to whomever's addon that was, but doing that is just dumb. ;)

That would be "polling the combat log" so definitely no :)