From: peter@transvirtual.com
Date: Thu Dec 10 1998 - 06:48:59 EST
Let me second that. I can give you even worse examples with redefined std funcs
- when you build a static kaffe version you can get even conflicts with
differently redefined allocators, since some of the external libs might come
with their own allocation schemes (e.g. libpng, libjpeg), possibly defined in
their headers. In this case, you can get different (runtime) behavior for
different linking (dynamic/static) *and* include order (lib header before/after
jni.h), and there is always a good chance of crashes.
Besides that, I wonder if it woudn't make sense to completely split
off memory requests which could be explicitly handled by the VM (not relevant
for gc) by means of two heap interfaces (object space, "conventional" space).
Always a good idea to keep the size of the gc-heap as small as possible.
-- Peter
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:11 EDT