GC is automatic - you can turn it off and call GCCollect manually but I don't recommend it.
You can keep an eye on it by using GCMemAlloced().
There is a new type of GC implemented in the threaded version of Blitzmax but that's for a different thread (pun).
In case you weren't aware, GC ditches objects when they go out of scope. In layman's terms, that means when you don't have anything pointing to an object (I.e. because you set it to Null as I mentioned earlier), GC throws it out and you lose whatever data was held there.
You can keep an eye on it by using GCMemAlloced().
There is a new type of GC implemented in the threaded version of Blitzmax but that's for a different thread (pun).
In case you weren't aware, GC ditches objects when they go out of scope. In layman's terms, that means when you don't have anything pointing to an object (I.e. because you set it to Null as I mentioned earlier), GC throws it out and you lose whatever data was held there.