This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: putenv() - copying environment string violates Unix specs?
- To: Andrej Borsenkow <Andrej dot Borsenkow at mow dot siemens dot ru>
- Subject: Re: putenv() - copying environment string violates Unix specs?
- From: Corinna Vinschen <vinschen at cygnus dot com>
- Date: Tue, 25 Jul 2000 14:04:26 +0200
- CC: cygwin <cygwin at sources dot redhat dot com>
- References: <001f01bff62c$c7b512f0$21c9ca95@mow.siemens.ru>
- Reply-To: cygwin <cygwin at sources dot redhat dot com>
Andrej Borsenkow wrote:
> > 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.
>
> Of course, then setenv() should never attempt to reuse old environment
> string. Just occured to me. That gives consitent handling - caller is
> responsible for allocating and freeing environment strings.
That's not required by SUSv2. If you call setenv you can't
influence memory usage in any way. See the glibc example.
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