Yup, in C/Cxx this mechanism would just be comparing the memory address of the function. What Galaxy is doing is completely unrelated and very different.
This appears to reveal the stack space remaining for Galaxy's memory.
To that, I give you...
intlibStack_SpaceRemaining=0;boollibStack_Helper(inti){libStack_SpaceRemaining=i;returntrue;}// Returns in bytes the free stack space remaining.intlibStack_GetFreeStackSpace(){if(libStack_Helper){}returnlibStack_SpaceRemaining;}
Call "libStack_GetFreeStackSpace()" to find out how much space you have left in the stack, in bytes. :)
Could be useful to some of these very large projects that think they're converging on that script limit.
Doesn't reveal the heap space remaining, though.
Also looks like for every level you go deeper into the call stack, you lose 28 bytes of the stack, excluding any parameters.
Yup, in C/Cxx this mechanism would just be comparing the memory address of the function. What Galaxy is doing is completely unrelated and very different.
This appears to reveal the stack space remaining for Galaxy's memory.
To that, I give you...
Call "libStack_GetFreeStackSpace()" to find out how much space you have left in the stack, in bytes. :)
Could be useful to some of these very large projects that think they're converging on that script limit.
Doesn't reveal the heap space remaining, though.
Also looks like for every level you go deeper into the call stack, you lose 28 bytes of the stack, excluding any parameters.