Flare
Stops copies me!
- Reaction score
- 662
Where would you ever need a limitless amount of variables? Having no limits is all fun and whatnot, but imposing reasonable 'limits' (e.g. what you expect/anticipate is required, with a buffer in case your expectation is less than actual) isn't really an issue if you're being limited by another factor which you may not have the luxury of increasing (e.g. a vast number of units on the map which begins to impede on map performance which is going to be more bothersome than a limitation on variable allocation).Also, why the hell would you ever LIMIT how many variables you can have... That makes NO SENSE what-so-ever...
Not having to worry about these things is nice, but I can't think of any situations (of the top of my head) where a limitation is detrimental. Feel free to add any that you think of though, I'd be interested to see.
To sum up - allocating a quantity of memory which you know damn well WON'T be used, that doesn't make any sense either.
8192^4? (I assume that 8292 is meant to be 8192) - if you're only permitted to allocate 2MB of memory to variables and, if you are correct in saying that'd it be ~500k, then how can the limit be 8192^4 (unless array allocation would differ from allocation of a number of non-arrayed variables equivalent to the size of the array). While the GUI may present it as possible (I don't think it'd have been the first time a particular value appeared to be valid, but was actually invalid), it may be impossible.In galaxy you can use a maximum size of 8192*8192*8192*8292 (actually thats the gui limit, dunno if you can add more with the script, never had the urge to test it).