Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <397D824A.44F1288@cygnus.com> Date: Tue, 25 Jul 2000 14:04:26 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Andrej Borsenkow CC: cygwin Subject: Re: putenv() - copying environment string violates Unix specs? References: <001f01bff62c$c7b512f0$21c9ca95@mow.siemens.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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