[Snippet] LocationUtils

[Alain.Mark]

Just a simple implementation of a location stack to help prevent location leaks.

library LocationUtils
//===========================================================================
//	"LocationUtils" by Alain.Mark
//
//	-Info-
//	 -Attempts to remove the problem of location leaks by providing a location stack.
//
//	-API-
//	 -function NewLocationEx takes real x, real y location
//	 -function NewLocation takes nothing returns location
//	 -function DestroyLocation takes location l returns nothing
//
//===========================================================================
	globals
		private integer N=0
		private location array Ll
	endglobals
	
//===========================================================================
	function NewLocationEx takes real x, real y returns location
		if(N==0)then
			return Location(x,y)
		endif
		set N=N-1
		call MoveLocation(Ll[N],x,y)
		return Ll[N]
	endfunction
	
//===========================================================================
	function NewLocation    takes nothing returns location
		return NewLocationEx(0.00,0.00)
	endfunction
	
//===========================================================================
	function DestroyLocation takes location l returns nothing
		set Ll[N]=l
		set N=N+1
	endfunction
	
//===========================================================================
endlibrary

 

[Bribe]

Recycling is mainly useful for:

Units (because creating them takes a lot of CPU)
Timers (because back in the day when TimerUtils used handle ID offsets, you wanted to preload them before the handle stack got too high, and destroying a timer without pausing it can cause it to still expire)
Groups (because once enumerating, there will be some small memory leaked when destroyed)

 

[Magtheridon96]

Locations are only useful for getting Terrain Z.
There are other uses that are notable and worthwhile, but the only resource that has taken advantage of that is Position :/

edit

Who needs group recycling
GLOBAL GROUPS FO EVA.

 

[Bribe]

The "GetUnitRallyPoint" native must be used in some cases as well, because there is no X/Y alternative there.

 

[Magtheridon96]

^ Problem Solved
http://www.hiveworkshop.com/forums/submissions-414/snippet-unitrallypoint-212285/

 

[WaterKnight]

Yeah, there is no need to have such a library. The concept is not new, location is a basic object. You do not need to create locations dynamically besides GetUnitRallyPoint maybe, which does not work here. It's not even always the best option to cache everything, creation and destruction of locations is cheap too. Only if you really want to use locations for whatever reason can this help to be safe of handle leaks.