From: Godmar Back (gback@cs.utah.edu)
Date: Wed Nov 25 1998 - 00:30:58 EST
I'm sure you've seen these warnings:
../../../../kaffe/libraries/clib/math/BigInteger.c: In function `Java_java_math_BigInteger_init0':
../../../../kaffe/libraries/clib/math/BigInteger.c:34: warning: implicit declaration of function `malloc'
../../../../kaffe/libraries/clib/math/BigInteger.c: In function `Java_java_math_BigInteger_finalize0':
../../../../kaffe/libraries/clib/math/BigInteger.c:48: warning: implicit declaration of function `free'
They're because Tim does a
#undef malloc
#undef free
to avoid getting our gc_malloc_fixed instead of the real thing.
Question a): Why wouldn't ours work?
Question b): What, if anything, does the JNI standard say about malloc/free?
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:04 EDT