Re: BigInteger.c

Date view Thread view Subject view Author view

From: Alexandre Oliva (oliva@dcc.unicamp.br)
Date: Wed Nov 25 1998 - 21:45:22 EST


On Nov 25, 1998, Godmar Back <gback@cs.utah.edu> wrote:

> 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?

mpz_get_str, in toString0, will definitely malloc() something, so we'd
better (free)() it (note parens to avoid macro expansion). I think
init0 and finalize0 could make use of garbage-collectable memory,
though (i.e., we could get rid of the other call to `free').

> Question b): What, if anything, does the JNI standard say about malloc/free?

I don't have the faintest idea :-)

-- 
Alexandre Oliva  http://www.dcc.unicamp.br/~oliva  aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
Universidade Estadual de Campinas, SP, Brasil


Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:57:04 EDT