Revision 850d2fec53ee188bab9e458f77906041ac7f1904 authored by Jeff King on 22 February 2016, 22:44:21 UTC, committed by Junio C Hamano on 22 February 2016, 22:50:32 UTC
There are many manual argv allocations that predate the
argv_array API. Switching to that API brings a few
advantages:
1. We no longer have to manually compute the correct final
array size (so it's one less thing we can screw up).
2. In many cases we had to make a separate pass to count,
then allocate, then fill in the array. Now we can do it
in one pass, making the code shorter and easier to
follow.
3. argv_array handles memory ownership for us, making it
more obvious when things should be free()d and and when
not.
Most of these cases are pretty straightforward. In some, we
switch from "run_command_v" to "run_command" which lets us
directly use the argv_array embedded in "struct
child_process".
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent b992657
| File | Mode | Size |
|---|---|---|
| bitmap.c | -rw-r--r-- | 5.0 KB |
| ewah_bitmap.c | -rw-r--r-- | 16.2 KB |
| ewah_io.c | -rw-r--r-- | 5.5 KB |
| ewah_rlw.c | -rw-r--r-- | 2.9 KB |
| ewok.h | -rw-r--r-- | 6.7 KB |
| ewok_rlw.h | -rw-r--r-- | 3.1 KB |
Computing file changes ...
