rdnzl-devel April 2007

rdnzl-devel@common-lisp.net

2 participants
2 discussions

[rdnzl-devel] A possible bugfix for a possible bug in IMPORT-ASSEMBLY
by Iver Odin Kvello 27 Apr '07

27 Apr '07

I think there is a bug in IMPORT-ASSEMBLY, in that the documentation says "Imports all public types of the assembly ASSEMBLY \(a string or a CONTAINER). If ASSEMBLY is a string then the assembly is first loaded with LOAD-ASSEMBLY. Returns ASSEMBLY as a CONTAINER." However, it doesn't seem to actually import the public types when the ASSEMBLY argument isn't passed to IMPORT-TYPE. Passing the assembly fixes this. Iver Odin Kvello iok(a)selvaag.no

2 1

[rdnzl-devel] A question about CAST
by Iver Odin Kvello 27 Apr '07

27 Apr '07

Hello, We've recently started using RDNZL for integration between an internal application written in ACL 7.0 and a CAD system using a .Net-based extension-layer in the latter; using .Net Remoting for communicating between the two systems. We've found that RDNZL works robustly, reliably and is very easy to use. Thank you very much for creating it. I have a question with regards to the action of the CAST operator: Currently, when CAST'ing from one .Net class to another, the type of the container is destructively updated; and there doesn't seem to be any way of copying a container so that a reference to the same object but with another type can be created. That is, I'd like to do something like (cast foo "SomeType")) (setq bar (copy-container foo)) (cast bar "SomeOtherType")) without the last operating also setting the type of FOO to SomeOtherType [1] Is there some idiom that would work like this that I've missed? If not, I guess the functionality would have to be added at the C++ level, which I haven't really looked at yet. Any pointers would be appreciated. Iver Odin Kvello iok(a)selvaag.no [1] The actual situation that came up was this: We have a remote object - actually a transparent proxy - of an interface-type WALL, and we need to get a reference to its lease. However, to to this we must cast the object to MarshalByRefObject, and if we use CAST to get this, it is impossible to CAST back to the original interface type. We did find a workaround: using System.Runtime.Remoting.RemotingServices.GetRealProxy, another copy of the transparent proxy is easily obtained, and that can be cast to a MBRO instead. But a copy/cast-operator would have been nicer.

2 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

rdnzl-devel April 2007