On Thu, Mar 30, 2017 at 12:56 AM, Jeff King <p...@peff.net> wrote: > But in the end it doesn't really matter. I think code like: > > const char *filename = git_path(...); > > or > > nontrivial_function(git_path(...)); > > is an anti-pattern. It _might_ be safe, but it's really hard to tell > without following the complete lifetime of the return value. I've been > tempted to suggest we should abolish git_path() entirely. But it's so > darn useful for things like unlink(git_path(...)), or other direct > system calls.
Yeah. I thought we killed most of those (was it your patches?). I had a quick look at "git grep -w git_path" again. The ones in builtin/am.c, builtin/grep.c and submodule.c look very much like that anti-pattern. The one in read_index_from() probably should be replaced with git_pathdup() as well. Sorry no patches (I'm very slow these days). -- Duy
