Fernando D. Mato Mira (matomira++at++lig.di.epfl.ch)
Thu, 22 Feb 1996 18:46:11 +0100
> where non-pfMalloc'ed data usually works. However, we've found that
> trying to support arbitrary data pointers is more trouble than
> it's worth. Consequently, 2.0 has a formal policy that all
> data supplied in the form of void*'s should be pfMalloc'ed.
Beign able to set up pfDeleteFunc, pfCopyFunc, pfPrintFunc, etc. on
a per-object basis does not seem like a lot of work (but you probably
want to store such pointers in a dynamically allocated `pfvtable', to
minimize overhead if you don't use such feature).
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:52:26 PDT