Quote:
Originally Posted by InfiniteDimensionality
A solution could be done in a library by writing a simple memory manager that returns unallocated regions of memory
|
There have been at least a couple of implementations of this. I haven't used
Tale's one, but their code generally looks good.
Personally, I just use a simple pattern like this in @init:
Code:
freemem = 0;
block1length = 3000; // or whatever
freemem = (block1buffer = freemem) + block1length;
// freemem now holds the next unallocated pointer, ready for block2
However, I assume from your extremely strong reaction that you have a whole litany of complaints against JS, not just this one issue with the memory block.
Given that, I'm not going to try and convince you why JS is wonderful - here are lots of other audio programming languages to try, and I believe many of them can be loaded as VSTs. Maybe one of those could work for you, although I wouldn't know what to recommend personally as I have been happily using JS for years.