Originally Posted by SDPhantom
That's the point though, it's not just memory. When the garbage collection is called more often, it eats up cycles and becomes a CPU problem.
|
Unless you can measure an actual impact from that, its still not a problem.
If you are extremely worried about the memory consumption from the Map APIs, you could use my Map library
HereBeDragons which offers table-free position APIs (althought thats not the reason I made it that way, its just the same API the library had in 7.x already) - and no, it also doesn't just wrap the Blizzard Map API to "hide" the tables.