[391] in Hesiod
Re: hesiod 3.x
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Jan 4 21:55:14 2000
Message-Id: <200001050254.VAA12618@small-gods.mit.edu>
To: "Danilo Almeida" <dalmeida@MIT.EDU>
cc: hesiod@MIT.EDU
In-Reply-To: Your message of "Tue, 04 Jan 2000 21:17:50 EST."
<DIEILAKKMPNAOBPOMHLBOEHKCAAA.dalmeida@mit.edu>
Date: Tue, 04 Jan 2000 21:54:22 -0500
From: Greg Hudson <ghudson@MIT.EDU>
> After quickly glancing around, I noticed that the 3.x interface has
> no hesiod_free to free strings. Are folks just supposed to use
> free?
Yup.
> If so, that's an API bug because it requires that my app use the
> same libc used by the hesiod library, which may be virtually
> impossible to guarantee in a portable manner in a fully dynamic
> library environment (Windows comes to mind).
What a crock. A library should be able to malloc() memory and have
the caller free() it.
(You can actually have two different libc implementations operating in
a program under Windows such that if the Hesiod library calls free()
it's a different function than if its caller does?)
