From ca5c701ca50c24807793294c5ed22230858ac5e6 Mon Sep 17 00:00:00 2001 From: Jeff King Date: Wed, 3 Aug 2016 19:01:42 -0400 Subject: write_or_die: drop write_or_whine_pipe() This function has no callers, and is not likely to gain any because it's confusing to use. It unconditionally complains to stderr, but _doesn't_ die. Yet any caller which wants a "gentle" write would generally want to suppress the error message, because presumably they're going to write a better one, and/or try the operation again. And the check_pipe() call leads to confusing behaviors. It means we die for EPIPE, but not for other errors, which is confusing and pointless. On top of all that, it has unusual error return semantics, which makes it easy for callers to get it wrong. Let's drop the function, and if somebody ever needs to resurrect something like it, they can fix these warts. Signed-off-by: Jeff King Signed-off-by: Junio C Hamano --- write_or_die.c | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'write_or_die.c') diff --git a/write_or_die.c b/write_or_die.c index 981687945..073443247 100644 --- a/write_or_die.c +++ b/write_or_die.c @@ -82,15 +82,3 @@ void write_or_die(int fd, const void *buf, size_t count) die_errno("write error"); } } - -int write_or_whine_pipe(int fd, const void *buf, size_t count, const char *msg) -{ - if (write_in_full(fd, buf, count) < 0) { - check_pipe(errno); - fprintf(stderr, "%s: write error (%s)\n", - msg, strerror(errno)); - return 0; - } - - return 1; -} -- cgit v1.2.1