X-Spam-Check-By: sourceware.org Message-ID: <4903.67.42.100.49.1170014267.squirrel@67.42.100.49> In-Reply-To: <20070128120735.GK27843@calimero.vinschen.de> 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> <45B540FF DOT 6060101 AT x-ray DOT at> <20070123083753 DOT GE27843 AT calimero DOT vinschen DOT de> <45B62E0B DOT 4080500 AT sh DOT cvut DOT cz> <45BBCF84 DOT 7070409 AT x-ray DOT at> <20070128120735 DOT GK27843 AT calimero DOT vinschen DOT de> Date: Sun, 28 Jan 2007 11:57:47 -0800 (PST) Subject: Re: Perl bug? From: "Yitzchak Scott-Thoennes" To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.5.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes 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 Corinna Vinschen wrote: > On Jan 27 23:17, Reini Urban wrote: >> Václav Haisman schrieb: >> >If I were you I would report it as a bug to their bug tracker. >> >> It's no bug, it's a perl feature, > > Uh, right, a *feature* ;) > >> and often defended. >> Even dll's are not unloaded. >> >> If you want to free it, free it explicitly with "undef" >> or with lexicals ("my") go out of scope. Doesn't help in this case, Reini. >> Same with PHP and python btw. Only GC languages like lisp, ml and its >> derivates have a proper GC. >> The perl GC they are talking about only "garbage collects" cyclic >> referenced objects on final destruction, to enable proper free() of >> externals. > > Thanks for the info. It's interesting to know. What I still don't get, > however, is the fact that the same statement does not waste memory on > the x86 Linux Perl 5.8.5, but does on the x86 Cygwin Perl 5.8.7 and the > x86_64 Linux 5.8.8. So it has been introduced only in later versions? > And why is it defended? It doesn't seem to make sense, rather on the > contrary. This behaviour hasn't changed that I know of. I verified that a 5.8.5 cygwin perl behaves the same way. Could you confirm your x86 Linux Perl 5.8.5 results again, and send me (privately if you wish) the output of: perl -MConfig=config_sh -we'print config_sh' from that perl? -- 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/