Getting the number of indexes in an array.

[Aanson]

Originally Posted by Seerah Ah, yes. And this. I honestly didn't scroll to see how many events you had in your table.

See my other post in this thread.

[Rainrider]

In case it's still unclear:

for i = 1, select("#", unpack(self.Events)) do

will result in what you seem to have expected from select. Don't do it that way though

[Vlad]

I'm sorry but this makes me cringe.

After I saw 'for i = 1, select("#", unpack(self.Events)) do' I had to write back!

Why not use the standard way of writing a table loop?

local events = {"A", "B", "C"}
for i = 1, #events do
  self:RegisterEvent(events[i])
end

The select function is great when fetching a specific argument returned from a function that returns a list of arguments, and using "#" returns how many arguments were returned.

function Events()
  return "A", "B", "C"
end

for k, v in ipairs({Events()}) do
  self:RegisterEvent(v)
end

Also this one works, not ideal but works. You encapsulate the returned arguments in a table and it will return the same table as in the first example. You then iterate it directly using ipairs.

In any case I find this to be a much better approach than unpacking the table to then use select "#" on it to iterate just over the index.

[Rainrider]

It seems 3 lines are too much to read, Vlad. What the TE seemed to expect select to return is actually the result of the code snippet I posted. Knowing how unpack works, helps understanding how select works. That was the point of my previous point. Maybe I failed at it, maybe not. I also stated (s)he should not use it like that. So please read before you criticize.

[Vlad]

To be honest I couldn't quite tell the purpose at first, so I hastily posted what my first gut feeling told me was the right response - sorry if I made you feel bad in any way!

[Phanx]

Originally Posted by Rainrider It seems 3 lines are too much to read, Vlad. What the TE seemed to expect select to return is actually the result of the code snippet I posted. Knowing how unpack works, helps understanding how select works. That was the point of my previous point. Maybe I failed at it, maybe not. I also stated (s)he should not use it like that. So please read before you criticize.

The problem with posting "bad" examples and saying "don't use this" is that -- as you yourself are complaining -- people don't actually read the "don't use this" part, and end up using your cringe-worthy anti-example as real code in their real addon. I make a habit of never posting functional code that should not actually be used, and I strongly recommend you (and everyone else) adopt this habit, too. If you want to show how something works, make up an example that wouldn't make you want to gouge your eyes out if you saw it in a real addon.

[Rainrider]

If a person comes to a medium for written communication to ask questions, I assume they do read. If they don't, it's all their fault.