Thread (32 messages) flat view 32 messages, 4 authors, 2016-06-15

Re: [PATCH 03/16] object_array: factor out slopbuf-freeing logic

From: Jeff King <hidden>
Date: 2016-06-15 23:02:40

On Tue, Oct 07, 2014 at 01:25:54PM +0200, Michael Haggerty wrote:
quoted
+static void object_array_release_entry(struct object_array_entry *ent)
+{
+	if (ent->name != object_array_slopbuf)
+		free(ent->name);
+}
+
Would it be a little safer to set ent->name to NULL or to
object_array_slopbuf after freeing the memory, to prevent accidents?
I considered that, but what about the other parts of object_array_entry?
Should we NULL the object context pointers, too?

The intent of this function is freeing memory, not clearing it for sane
reuse.  I think I'd be more in favor of a comment clarifying that. It is
a static function used only internally by the object-array code.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help