I hate lua.

[shouryuu]

function GetGuilNumbers()
    numGuildMembers = GetNumGuildMembers();
	for i=1,numGuildMembers do
	name[i], _, _, _, _, _, _, _, _, _= GetGuildRosterInfo(i);
	end
end

function SetTicketNumberToNil()
	for k,v pairs do
		name[k]=name[v]
	end
end

Does the above set the name table's keys as it's values, and it's values as it's keys,making it look like this:

Keys        Values
name1       1
name2       2
name3       3
.......         ...
.......         ...
nameN       N

Or does it change it to the following

Keys        Values
name1     name1
name2     name2
name3     name3
.......         ...
.......         ...
nameN       nameN

[shouryuu]

Second question:

local name{}
function GetGuilNumbers()
    numGuildMembers = GetNumGuildMembers();
	for i=1,numGuildMembers do
	name[i], _, _, _, _, _, _, _, _, _= GetGuildRosterInfo(i);
	end
end

function SetTicketNumberToNil()
	for k,v pairs do
		name[k]=name[v]
		name[v]=0
	end
	for i=1,numguildMembers do
		table.insert(EasierFrameShowing[i],name[i])
end

Will I end up with a table which would look like this:

EasierFrameShowing
      |-Key=1 Value=Name 
                                      | Key = Name[1]  (for example shouryuu)
                                      | Value = Name[1] (should be 0)

Or something else?

[Cladhaire]

The first question is.. what are you trying to accomplish.

The first example looks like you'd get the folllowing:

You have name, which you populate with numerically indexed names of the members in the raid. So if its you and I.. we'd be:

name = {[1] = "Cladhaire", [2] = "Shouryuu"]}

Then your code does something that I'm not understanding. You go through and set the table to the following:

name = {[1] = nil, [2] = nil};

Because name[v] doesn't have a value. if you're looking to make a double-reverse-lookup table, you can use:

function SetTicketNumberToNil()
	for k,v in name do
		name[v]=name[k]
	end
end

But I'm not sure exactly what you're looking for. My code would give you:

name = {
[1] = "Cladhaire",
[2] = "Shouryuu",
["Cladhaire"] = 1,
["Shouryuu"] = 2,
};

[Cladhaire]

Second Question

First step, you build the table indexed by raidnumber. All is well and good.

Then you go through and do the same thing as before, setting name[1] and name[2] to nil.
Then you go and set name["Cladhaire"] and name["Shouryuu"] to 0;

The last bit of code makes the following in EasierFrameShowing:

EasierFrameShowing = {[1] = nil, [2] = nil};

[shouryuu]

Hummm ponder ponder... I'll take some time to think about this and hit ya with another question if I fail :P

[Cladhaire]

It more comes down to what you're trying to accomplish =).

[shouryuu]

It's simple enough I want to inverse a table's keys and values. I want the keys to become the values, and the values to become the keys.

Would something along these lines work?

function SetTicketNumberToNil()
	for k,v pairs do
		table.insert(name, name[i], i)
	end
end

This only work, if it does, because the keys are simple: 1,2,3,4,5... But how do I do that if I have keys like zdfs and gkfslg; or djakf?

[Trimble Epic]

here's how I would do what I think you're trying to do

function SetTicketNumberToNil(name)
	local new_name = {}  -- use a temporary table
	for k,v in name do -- iterate over every field in the table
		new_name[v]=k -- just stick 'em in the new table
	end
	table.setn(new_name,table.getn(name)) -- might not be needed, but you can do this to be thorough
	return new_name -- return the new table
end

[shouryuu]

ugh i feel so stupid... :P well thanks!

EDIT: I'm keeping the dumb questions flowing. Is the "for k,v" statement general? By that I mean does it work for every table, or is it an example everyone takes and everyone understands?

[Trimble Epic]

the common notation 'for k,v in table do' is used because it's easy to read/recognize.

Whenever you use the 'generic' form of the for statement on a table WITHOUT an iterator (i.e. 'for k,v in table' vs. for 'k,v in pairs(table)' ), the for statement automatically provides 2 variables for each run through the loop - the key and it's associated value - thus k and v. When we (teachers?) give helpful examples, we commonly use k,v to emphisize the key and the value inside the sample.

yes, 'for k,v...' works on every table.

[shouryuu]

Cool, thanks a lot! i don't understand why tables are giving me so much trouble...

[Trimble Epic]

My pleasure.

I really like the way tables work. They are remarkably versatile.