On Sun, 10 Oct 1999, Godmar Back wrote: > > Chris Toshok wrote: > > > precise gc is impossible with the possibility of arbitrary C code in native > > > methods. > > > > I don't think that's true. The stuff about local and global references in > > the JNI spec makes provisions for this. > > Hence the word "arbitrary" in Chris's statement: > JNI provides guidelines for C code to allow precise gc. Right. I thought Chris might mean that some non-precise technique, like scanning the C stack or heap for possible Java object references, would be necessary, and I just wanted to clarify that it isn't. Ill-behaved native code can leak memory or hold on to invalid references, but then again, ill-behaved native code can do plenty of other bad things, so it's not really even worth mentioning.
