Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <397D6B77.51D3B6A6@cygnus.com>
Date: Tue, 25 Jul 2000 12:27:03 +0200
From: Corinna Vinschen <vinschen@cygnus.com>
Reply-To: cygwin <cygwin@sources.redhat.com>
MIME-Version: 1.0
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
CC: Cygwin@Sourceware.Cygnus.Com
Subject: Re: putenv() - copying environment string violates Unix specs?
References: <000e01bff606$02e2d500$21c9ca95@mow.siemens.ru>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Andrej Borsenkow wrote:
> 
> According to putenv() description SUS V2, the argument is used "as is"
> and never copied. Cygwin version of putenv() explicitly copies argument
> (actually, multiple times - first in putenv() and then in setenv()).
> This is horribly confusing for programs that expect to manage
> environment strings themselves and/or have own memory allocator (like
> Zsh). It means, that every use must be checked and free'ing of
> environment string put under #ifdef __CYGWIN__
> 
> Is there any particular reason for this? Is there any chance that it may
> be changed to be more Unix-compatible?

You're right and I think it should possible to change that but
I'm not sure if that will make it into 1.1.3.

Corinna

-- 
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com