Re: [PATCH 03/16] object_array: factor out slopbuf-freeing logic
- From
Michael Haggerty <mhagger@alum.mit.edu>
- Date
- Oct 7, 2014, 11:25 UTC
- Message-ID
- <5433CDC2.6000908@alum.mit.edu>
- In-Reply-To
- <20141003202222.GC16293@peff.net>
On 10/03/2014 10:22 PM, Jeff King wrote:
Show 23 quoted lines
> This is not a lot of code, but it's a logical construct that
> should not need to be repeated (and we are about to add a
> third repetition).
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> object.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/object.c b/object.c
> index ca9d790..14238dc 100644
> --- a/object.c
> +++ b/object.c
> @@ -355,6 +355,12 @@ void add_object_array_with_context(struct object *obj, const char *name, struct
> add_object_array_with_mode_context(obj, name, array, S_IFINVALID, context);
> }
>
> +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?
> [...]
Michael
-- Michael Haggerty mhagger@alum.mit.edu