On Wed, Mar 04, 2009 at 05:38:47PM -0500, Jonathan S. Shapiro wrote: > So basically, your concern is that if we insist on GC, we can't deploy on > iPhone?
(I'm not sure I really understand in what practical situations a GC would be forced upon the user, so it may not be a real problem in the following contexts. If avoiding the GC just means not escaping closures, that's no big deal. The way C++0x handles closures is not pretty, but works in these contexts.) What about embedded application on platforms with just a few hundred KB of RAM (no disk or secondary storage)? What about hard real-time applications? How do you do GC across many many CPU cores? As a related question, what's going to be the size of BitC's runtime? Can we expect a notion similar to freestanding environments as in C? (similar in its resource requirements) Thanks. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
