> It's a prior constraint in the BitC discussion that we will have a memory > safe language. At the moment, that means GC or RC.
A clueless and out in left field question: Erlang seems to get soft-real-time 'easily' by having heaps per actor, and when the actor dies the individual heap gets collected (e.g.: http://prog21.dadgum.com/16.html). I realize BitC is not an actor language nor would the design of BitC try to be actory underneath and C style on top. But I wonder if there's a path for something like Erlang's approach to become useful for system programming. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
