If this is the case, then that is fantastic. My BitC implementation may be out of date, but I thought it was attempting to link to libgc, or offered a no-gc lib which duplicated the symbols used from libgc. I may be confusing this with something completely different.
On Wed, Mar 4, 2009 at 4:59 PM, Geoffrey Irving <[email protected]> wrote: > On Wed, Mar 4, 2009 at 1:20 PM, Rick R <[email protected]> wrote: > >> > >> I would be very interested to know which situations *you* have in > >> mind, and *why* GC is inappropriate for those situation. > > > > Cell Phone Applications. Three reasons: > > > > 1: The iPhone docs (but not the official agreement) disallows GC. The > > default garbage collector for the Cocoa SDK is disabled in the iPhone > SDK. > > Using alternate forms of GC is discouraged. > > > > 2: Dynamic Linking is disallowed in official iPhone apps. So using a GC > as > > an .so (which is commonly done with the boehm GC) is disallowed. This is > > obviously easy to work around. > > > > 3: The Boehm conservative GC is, well, quite conservative. Memory is > still a > > limited resource (and paging not an option) on handheld platforms. > > None of these reasons apply, since bitc is using its own type-directed > garbage collector, not a separate conservative collector. Therefore, > the garbage collection should be baked into the generated C source > during translation. > > Geoffrey > _______________________________________________ > bitc-dev mailing list > [email protected] > http://www.coyotos.org/mailman/listinfo/bitc-dev > -- We can't solve problems by using the same kind of thinking we used when we created them. - A. Einstein
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
