Y-Less
Y-Less
What?
Yes, I got that, but just saying "it crashes" is not helpful at all. I need something that can reproduce the crash, an idea of what libraries you are using,...
Ahh yes, of course that's why! That's helpful.
OK, I'm a bit stumped actually, the idea I had didn't work, so I need to think some more.
I've put `YSI_NO_HEAP_MALLOC` back in. That was always the vastly more stable method.
I also just discovered that the default slop space (space reserved in the heap for callback parameters) was very small (only ~256 bytes (just 64 cells)), which will be blown...
Basically, the new version uses the heap, but the VM clears the heap at the end of every top-level callback (easy way to ensure consistency). So every time a new...
That callback isn't in the library at all.
The code is MPL, so we can use it just fine (as long as any modifications to individual files are fed back to the parent project).