WoW:USERAPI EraseTable - Revision history

Move page script: Move page script moved page USERAPI EraseTable to WoW:USERAPI EraseTable without leaving a redirect

2023-08-15T04:49:11Z

Move page script moved page USERAPI EraseTable to USERAPI EraseTable without leaving a redirect

← Older revision	Revision as of 04:49, 15 August 2023
(No difference)

Bear at 07:29, 21 September 2013

2013-09-21T07:29:01Z

← Older revision		Revision as of 07:29, 21 September 2013
Line 1:		Line 1:
	{{~~localuserfunc~~}}		{{userfunc}}

	'''EraseTable''' erases a table, often a good way to reduce garbage creation. Note that erasing a table can be more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also, note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.		'''EraseTable''' erases a table, often a good way to reduce garbage creation. Note that erasing a table can be more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also, note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.

WoWWiki>Egingell: Moving "talk" to Talk page.

2009-12-31T00:14:59Z

Moving "talk" to Talk page.

← Older revision		Revision as of 00:14, 31 December 2009
Line 8:		Line 8:
	for i in pairs(t) do t[i] = nil end		for i in pairs(t) do t[i] = nil end
	end		end



	~~----~~
	~~Would think [[API_wipe#Notes\|wipe(t)]] would be more effective.~~

	~~--[[User:MichaelLundRasmussen\|MichaelLundRasmussen]] ([[User talk:MichaelLundRasmussen\|talk]]) 13:10, December 30, 2009 (UTC)~~

WoWWiki>MichaelLundRasmussen: Added comment about a more effective way to erase a table

2009-12-30T13:10:28Z

Added comment about a more effective way to erase a table

← Older revision		Revision as of 13:10, 30 December 2009
Line 8:		Line 8:
	for i in pairs(t) do t[i] = nil end		for i in pairs(t) do t[i] = nil end
	end		end



			----
			Would think [[API_wipe#Notes\|wipe(t)]] would be more effective.

			--[[User:MichaelLundRasmussen\|MichaelLundRasmussen]] ([[User talk:MichaelLundRasmussen\|talk]]) 13:10, December 30, 2009 (UTC)

WoWWiki>Rolandius: WW:MOS

2009-04-27T05:45:33Z

WW:MOS

← Older revision		Revision as of 05:45, 27 April 2009
Line 1:		Line 1:
	{{localuserfunc}}		{{localuserfunc}}

	~~Erases~~ a table, often a good way to reduce garbage creation. Note that erasing a table can be more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.		'''EraseTable''' erases a table, often a good way to reduce garbage creation. Note that erasing a table can be more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also, note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.

	For more details on the inner workings of tables and when to reallocate vs when to erase, see [[Lua object memory sizes]] and it's [[Talk:Lua object memory sizes\|talk page]].		For more details on the inner workings of tables and when to reallocate vs when to erase, see [[Lua object memory sizes]] and it's [[Talk:Lua object memory sizes\|talk page]].

WoWWiki>Pcj at 18:29, 28 January 2008

2008-01-28T18:29:37Z

← Older revision		Revision as of 18:29, 28 January 2008
Line 1:		Line 1:
	{{localuserfunc}}		{{localuserfunc}}
	~~__NOTOC__~~

	Erases a table, often a good way to reduce garbage creation. Note that erasing a table can be more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.		Erases a table, often a good way to reduce garbage creation. Note that erasing a table can be more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.

WoWWiki>Tekkub at 20:20, 11 January 2008

2008-01-11T20:20:54Z

← Older revision		Revision as of 20:20, 11 January 2008
Line 1:		Line 1:
	{{~~userfunc~~}}		{{localuserfunc}}
	__NOTOC__		__NOTOC__

	Erases a table, often a good way to reduce garbage creation. Note that erasing a table ~~is generally~~ more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.		Erases a table, often a good way to reduce garbage creation. Note that erasing a table can be more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.

			For more details on the inner workings of tables and when to reallocate vs when to erase, see [[Lua object memory sizes]] and it's [[Talk:Lua object memory sizes\|talk page]].

	local function EraseTable(t)		local function EraseTable(t)
	for i in pairs(t) do t[i] = nil end		for i in pairs(t) do t[i] = nil end
	end		end

WoWWiki>Mikk: Add note that hashes never shrink

2007-12-31T16:23:52Z

Add note that hashes never shrink

← Older revision		Revision as of 16:23, 31 December 2007
Line 2:		Line 2:
	__NOTOC__		__NOTOC__

	Erases a table, often a good way to reduce garbage creation. Note that erasing a table is generally more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table.		Erases a table, often a good way to reduce garbage creation. Note that erasing a table is generally more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table. Also note that a hash (as opposed to a 1..n integer-index) will NEVER SHRINK. Each key you ever used will use ~40 bytes and keep doing so until the table is destroyed. If you re-use the same keys this is obviously a nonissue.

	local function EraseTable(t)		local function EraseTable(t)
	for i in pairs(t) do t[i] = nil end		for i in pairs(t) do t[i] = nil end
	end		end

WoWWiki>Tekkub at 01:18, 12 February 2007

2007-02-12T01:18:41Z

New page

{{userfunc}}
__NOTOC__

Erases a table, often a good way to reduce garbage creation. Note that erasing a table is generally more expensive than letting the GC system reclaim it, so one might prefer simply reallocating a new empty table.

local function EraseTable(t)
for i in pairs(t) do t[i] = nil end
end