[bitc-dev] Pools in lieu of GC
raould at gmail.com
Wed Mar 4 21:00:15 EST 2009
> If you allocate *anything* on the heap, you will eventually GC. It
> does not matter if you are allocating closures or something else.
at least for me, i think there is some amount of terminology confusion
hindering my understanding here.
* C++ lets me allocate on the heap, but doesn't force me to use GC. (i
am not saying that as if it is either a good or bad thing, btw.)
* you might be talking about Bit-C in particular, that it enforces
that anything on the heap can only be freed via the GC system?
More information about the bitc-dev