Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!seismo!rochester!pt.cs.cmu.edu!ius2.cs.cmu.edu!edw
From: edw@ius2.cs.cmu.edu.UUCP
Newsgroups: comp.lang.c
Subject: Lisp-C interface
Message-ID: <1067@ius2.cs.cmu.edu>
Date: Fri, 13-Mar-87 12:04:20 EST
Article-I.D.: ius2.1067
Posted: Fri Mar 13 12:04:20 1987
Date-Received: Sat, 14-Mar-87 09:26:08 EST
Organization: Carnegie-Mellon University, CS/RI
Lines: 17
Keywords: lisp C malloc


      
   Question to thoses of you that are familiar with Sun's Common Lisp and
its foreign function call feature.

   I am designing an interface in lisp to a library written in C.  There is
no problem calling the C functions, the problem is that this library
extensively uses malloc and free.  As I have been told by other people,
when lisp goes to garbage collect, it also collects the memory that
was allocated by malloc (all memory up to sbrk).  

    One, is this true?
    Second if so are there any plans to fix it so malloc will work right
    or am I stuck re-implementing malloc.


						Eddie Wyatt