> Don't sweat system malloc behaviour all that much at the moment. We are
> going to be completely taking over memory allocation internally at some
> point reasonably soon, so as long as what you do doesn't crash we should
be
> fine. (It's OK to leak at this point--either the GC system or the Big
> Mallet of Programming Correctness will fix the problem... :)
Since we are going to use some kind of GC, we will get rid of malloc anyway.
Most of the current code are not gc safe, so we have to rewrite them.
Once the core is stable, we can start using a simple mark-sweep collector
as the default gc.
Hong
