[stjobe]

I'm not sure what you're trying to achieve, as nilling the table effectively deletes it (it will be garbage collected eventually).

for k,_ in pairs(someTable) do 
    someTable[k] = nil 
end

should do the trick; someTable is now empty and will be disposed of in time.

As for printing out the values of your table containing tables and functions, there's a slight hitch; you can't get the source code for functions back after compilation to byte-code. Tables should be easy enough though:

Example:

t = {}
 
function t.someFunction()
    local var = 13
    print(var)
end
 
t.someTable = {}
t.someTable.alpha = "tableEntry 1"
t.someTable.beta = "tableEntry 2"
 
for k,v in pairs(t) do
    print(k) -- gives the key, e.g. "someTable" or "someFunction"
    print(v) -- gives the value, e.g. "table: 0x04E50778" or "function: 0x04EF298" 
    print(t[k]) -- same as "print(v)"
    if type(v) == "table" then -- we can iterate over tables
        for l,_ in pairs(v) do
            print(l..": "..v[l])
        end
    elseif type(t[k]) == "function" then -- but not over functions
        print("source code isn't available")
    end
    print("---")
end

Which should output something similar to:

someTable
table: 0x04C3E578
table: 0x04C3E578
alpha: tableEntry 1
beta: tableEntry 2
---
someFunction
function: 0x04E518F8
function: 0x04E518F8
source code isn't available
---

Also, you don't strictly need two variables to pairs(), but it's considered good practice to replace the unneeded variable with underscore. The following three snippets do the same thing:

for k,v in pairs(t) do
    t[k] = nil
end
 
for k in pairs(t) do
    t[k] = nil
end
 
for k,_ in pairs(t) do
    t[k] = nil
end

It's the same for any function; you don't have to store all their return values - you'll get as many from the start of the list of return values as you declare variables for, and the rest will be ignored. In most cases it's proper to replace the unneeded return values with underscore, but in other cases that just makes for unreadable code.

For instance, GetUnitBuffInfo() returns ten values, but if I'm only interested in the name of the buff (which is first on the list of return values), it's perfectly fine to use it like this:

local buffName = GetUnitBuffInfo("player", 1)

instead of the slightly ridiculous

local buffName, _, _, _, _, _, _, _, _, _ = GetUnitBuffInfo("player", 1)

or even more ridiculous naming nine variables I won't ever use.

It gets a bit messier if I'm only interested in the last return value though...