The purpose of this note is to explain how to write functions that allocate memory. One basic principle is that one should see the garbage collector as an adversary, which always tries to deallocate memory. You should protect your data against it. Here are a few examples. Continue reading
Contrarily to all versions of OrchIDS ≤1.1, OrchIDS 2.0 has garbage-collected memory.
This means that you still allocate memory, but do not deallocate it explicitly. This imposes a certain number of constraints on the way you program. Continue reading