From: Godmar Back (gback@cs.utah.edu)
Date: Wed Dec 09 1998 - 16:30:59 EST
Ideally, a jni compliant native library would include jni.h,
and should otherwise be unaffected ANSI C or C++ code.
That is, we cannot tell programmers "use or don't use a given function
that's part of ANSI C". Or "include jni.h before you do, but if you
must call the `real' free, #undef free" ...
Do you see my point?
- Godmar
>
> Godmar Back writes:
> > Could we come up with a set of rules as to when to include "config.h"
> > and when not, and also a statement about the malloc redefinition issue?
> > I think #define malloc if you include "jni.h" might just be plain wrong?
> > It seems it's a big mess at this point.
>
> Why don't we just avoid using "malloc" everywhere in the source tree
> (except the GC). Use "kmalloc" instead or something.
>
> I think redefining things that this is extremely misleading. Same
> thing goes for "read", "write", etc.. Why not "kread", "kwrite" ??
>
> -Archie
>
> ___________________________________________________________________________
> Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
>
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:09 EDT