User talk:Nekhanimal

GetNextRef

Looking the OBSE source code for GetNextRef, it should not compile with arguments, as you noted. For that reason, I've reverted your edit to the page. Please confirm that you are using either v0018 or the v0019 beta versions of OBSE, as this may be an obsolete bug. If you are, we can put that note back, at least until I get a chance to test it myself.

Regardless, thank you for helping to improve the Wiki. Any edit (well, barring spam or vandalization) is a very good thing, and I thank you for yours. Even if you were mistaken, double-checking is always good. Thank you.
Dragoon Wraith TALK 20:32, 15 August 2010 (EDT)

Aha!

That was an amazingly quick response! I can assure you I am indeed using OBSE v0019 at the time of writing. Here is the script I was trying to debug, along with the culprit GetNextRef:

http://forums.bethsoft.com/index.php?/topic/1110628-is-this-correct-array-usage-need-protips/

It's the block in the middle. Adding parameters to GetNextRef there will compile, but crash when the script tries to access Foo. The rest of the script runs fine. By the way, must the array be Constructed only once to avoid memory bloat, or is there a deconstructor for when an already constructed array var is constructed again?

Arrays are "smart pointers", so they will keep track of destructing themselves as necessary (OBSE tracks which variables are pointing to which arrays, and when none are left the array is destroyed). So you don't need to worry about that.

GetNextRef uses the parameters passed to GetFirstRef, so there's no need to re-supply them. The fact that the compiler let you is, as far as I can tell, a bug. I'd recommend asking Scruggs about it in the thread.

Dragoon Wraith TALK 20:59, 15 August 2010 (EDT)

Thanks for your time, glad it got sorted out!