Path: utzoo!attcan!uunet!munnari.oz.au!metro!cluster!necisa!boyd
From: boyd@necisa.ho.necisa.oz (Boyd Roberts)
Newsgroups: comp.lang.c
Subject: Re: free (NULL)
Message-ID: <1753@necisa.ho.necisa.oz>
Date: 5 Jun 90 01:12:10 GMT
References: <1771@mindlink.UUCP> <NUG33GF@xds13.ferranti.com> <2574@skye.ed.ac.uk> <1743@necisa.ho.necisa.oz> <3124@goanna.cs.rmit.oz.au>
Organization: NEC Information Systems Australia Pty. Ltd.
Lines: 18

In article <3124@goanna.cs.rmit.oz.au> ok@goanna.cs.rmit.oz.au (Richard A. O'Keefe) writes:
>Somewhere the context seems to have been lost.  I wasn't talking about
>library routines to create single objects, but library routines to manage
>a collection of objects (think of hsearch and the like) where the objects
>     4. Are sometimes things that the caller provided (whatever they are)
>        and sometimes things that the package mallocked

As I've said before, what you require is an interface.  A clearly defined,
clean interface.  No more, no less.  You'll just have to bite the bullet
for existing routines that don't provide the interface you want.  For
future routines, you define the interface.

Just define the interface.


Boyd Roberts			boyd@necisa.ho.necisa.oz.au

``When the going gets wierd, the weird turn pro...''