This is the current implementation. We're going to replace this with an effect-style analysis.
On Wed, Mar 4, 2009 at 4:51 PM, Swaroop Sridhar <[email protected]> wrote: > Rick R wrote: >> I would be happy to use BitC a feature limited mode. It would be nice if >> there were a "strict" compiler option that would warn me if I were to >> use a construct that required malloc. > > There is a compiler option --no-alloc, which precludes dynamic > allocation. This mode rejects any expression that could cause run-time > allocation, including closure construction. The analysis is conservative > in the sense that all expressions that construct closures are rejected, > regardless of whether the closure escapes or not. > > Swaroop. > _______________________________________________ > bitc-dev mailing list > [email protected] > http://www.coyotos.org/mailman/listinfo/bitc-dev > > _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
