May 2007 - rdnzl-devel@lists.common-lisp.net

[rdnzl-devel] Possible leak with RDNZL 0.11.0/Lispworks 5
by Matthew Lamari 20 May '07

20 May '07

First off, thanks all for such useful bridging software. I converged on this after seeing leaks in my interactions with a DLL. My actual leak seems to occur on cast/unbox. However, in understanding what I may or may not be doing wrong, I present this situation: (loop for i from 0 do (rdnzl::invoke (rdnzl::invoke "System.Guid" "NewGuid") "ToString")) Nothing particularly inherent to Guids, just an example I could find that returns a string. This loop sits there eating up Ram in a situation where I'm guessing it shouldn't. Putting garbage collects in the middle of its execution doesn't change this, nor does running GC/clean-down after breaking out. I'm talking about post-collect menory usage continously rising. It stereotypes a situation in my usage pattern of calling into dotnet and returning strings. Is there something I'm doing wrong? An incorrect assumption about dotnet? Any help appreciated. Thanks, Matt

2 2

[rdnzl-devel] New patch for a COPY-CONTAINER operator
by Iver Odin Kvello 18 May '07

18 May '07

Here are a couple of patches to implement the COPY-CONTAINER operator I missed. I hope I got things right with the formatting and the diffs and so forth. I did test the thing for the getting-the-lease-object problem, and it worked as it should, in that (cast (invoke (cast (copy-container w) "System.MarshalByRefObject") "GetLifetimeService") "System.Runtime.Remoting.Lifetime.ILease") .. will return the correct lease for the remote object w. A potential issue: I had to rename the copier-function of the CONTAINER-struct to be able to use the COPY-CONTAINER name. I couldn't think of a good alternative, and the struct-copy function wasn't actually in use, so I figured maybe it was ok. Regards, Iver Odin Kvello iok(a)selvaag.no

2 2

[rdnzl-devel] A patch for CAST to enable casting to types from assemblies loaded using LoadFrom
by Iver Odin Kvello 11 May '07

11 May '07

Hello, Here is another set of patches that fixes a small issue with CAST: the current CAST uses GetType with an assembly-qualified type-name only, and therefore will not work with types in an assembly loaded using System.Reflection.Assembly.LoadFrom and similar. The patch makes CAST use a Type-object directly if passed one instead of a type-name, like NEW already did. That is, one can do (setf assembly (invoke "System.Reflection.Assembly" "LoadFrom" url)) (setf mytype (invoke assembly "GetType" sometypename)) (cast someobject mytype) This should be the minimal neccessary support for these kinds of assemblies in case they are needed for an application. Regards, Iver Odin Kvello iok(a)selvaag.no

1 0