Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Subject: Re: [PATCH] setup.exe: removes some memory leaks from fromcwd.cc
From: Robert Collins <robert.collins@itdomain.com.au>
To: cygwin@cygwin.com
In-Reply-To: <20011105115003.A19389@redhat.com>
References: <3BE2CC48.47462EC6@syntrex.com>
	<1004743324.9086.39.camel@lifelesswks> <3BE6642E.9AA62568@syntrex.com>
	<1004997932.1663.2.camel@lifelesswks> <3BE68FC5.C7CDF863@syntrex.com>
	<1005000062.1663.8.camel@lifelesswks>  <20011105115003.A19389@redhat.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/0.15 (Preview Release)
Date: 06 Nov 2001 08:56:28 +1100
Message-Id: <1004997389.4534.3.camel@lifelesswks>
Mime-Version: 1.0
X-OriginalArrivalTime: 05 Nov 2001 22:02:36.0189 (UTC) FILETIME=[93D23CD0:01C16645]

On Tue, 2001-11-06 at 03:50, Christopher Faylor wrote:
...
> >I'm really not worried about cleaning up globals at exit - I'm much
more
> >warried about cleaning up globals as we go, or as we change from dialog
> >to dialog. Exit is a trapdoor, so it cannot be a 'problem'.
> 
> Since the memory is going to be freed on exit anyway, I don't see any reason
> to go to great lengths to invent a system for freeing it.
> 
> setup.exe is a short-lived program.  We should be good about freeing up memory
> that we use because that's good programming but I don't think we have to
> invent some kind of garbage collection system to deal with this.

I think we are agreeing again, no?

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

