X-Spam-Check-By: sourceware.org Date: Wed, 24 Jan 2007 11:05:40 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Perl bug? Message-ID: <20070124100540.GP27843@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20070122181727 DOT GC27843 AT calimero DOT vinschen DOT de> <1552 DOT 67 DOT 40 DOT 28 DOT 188 DOT 1169493973 DOT squirrel AT 67 DOT 40 DOT 28 DOT 188> <20070122202137 DOT GC20665 AT calimero DOT vinschen DOT de> <3593 DOT 67 DOT 40 DOT 28 DOT 188 DOT 1169584799 DOT squirrel AT 67 DOT 40 DOT 28 DOT 188> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3593.67.40.28.188.1169584799.squirrel@67.40.28.188> User-Agent: Mutt/1.4.2.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Jan 23 12:39, Yitzchak Scott-Thoennes wrote: > [...] > Right, *each* x operation has it's own target. If you undef $a, $b, etc. > at the end and wrap the whole thing in a for (1..2) loop, you'll see the > second time round that space is only allocated once per statement. > Or just have one x operation, and only see the "leaked" memory allocated > once: > [...] > There has been some work towards implementing a "use less 'memory';" pragma > that may make perl less greedy, but there's no timetable for that or clear > plan for what it would do. Thanks for the description, that's helpful. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/