From jlbprof at gmail.com Fri Jul 21 04:39:20 2017 From: jlbprof at gmail.com (Julian Brown) Date: Fri, 21 Jul 2017 06:39:20 -0500 Subject: [pm-h] Saw this on Reddit Message-ID: https://www.reddit.com/r/perl/comments/6ojrau/perl_vs_clojure/ Thought you might like that. Julian -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrdvt92 at yahoo.com Wed Jul 26 08:52:19 2017 From: mrdvt92 at yahoo.com (Michael R. Davis) Date: Wed, 26 Jul 2017 15:52:19 +0000 (UTC) Subject: [pm-h] Perl Win32::OLE issue with custom dll References: <565678248.1279587.1501084339591.ref@mail.yahoo.com> Message-ID: <565678248.1279587.1501084339591@mail.yahoo.com> Folks,I have an application that I'm supporting and it has a memory leak involving Win32::OLE. ? ?The only thing that clears up the memory leak is stopping the Perl application and restarting it. ?But, there has got to be a way to clean up the process at run-time if stopping the Perl process cleans it up. right? Is there possibly a way to unload Win32::OLE and then re-load it? ?This is the high level process but for some reason the DLL is not cleaning up on object destruction like it should. ?Has anyone worked with this kind of thing before? Simplified code... my $report ? = Win32::OLE->new($class) or die(sprintf("Error: %s. Cannot create object for class %s.", Win32::OLE->LastError, $class)); $rpt->Export($ext, $filename); #Method from dll $report = undef; #code in DLL is supposed to clean up itself when it goes out of scope Thanks, Mike CPAN: mrdvt -------------- next part -------------- An HTML attachment was scrubbed... URL: