Re: [PATCH] Use setenv(), fix warnings

From: Junio C Hamano <junkio@cox.net>
Date: Feb 26, 2006, 18:06 UTC
Message-ID: <7vmzge570u.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060226171346.33ad3e47.tihirvon@gmail.com>

Timo Hirvonen <tihirvon@gmail.com> writes:

>   - Use setenv() instead of putenv()
>   - Fix -Wundef -Wold-style-definition warnings
>   - Make pll_free() static

I think the last one makes sense, and I can see why some people may prefer -Wundef but I am not sure about the first one. Care to defend why we should prefer setenv()? IIRC, initially we did not use setenv() anywhere because certain platforms only had putenv().

Show 7 quoted lines

> diff --git a/fsck-objects.c b/fsck-objects.c
> @@ -483,7 +483,7 @@ int main(int argc, char **argv)
>  	if (standalone && check_full)
>  		die("Only one of --standalone or --full can be used.");
>  	if (standalone)
> -		putenv("GIT_ALTERNATE_OBJECT_DIRECTORIES=");
> +		setenv("GIT_ALTERNATE_OBJECT_DIRECTORIES", "", 1);

For platforms with only putenv we did this; here, what we really wanted to do was unsetenv.