Re: [IronPython] Revisiting interfaces and COM

2009-03-17 Thread Alex Willmer
2009/3/16 Dino Viehland di...@microsoft.com: The resolution of that bug was that we now expose explicitly implemented interfaces automatically if there are no naming conflicts.  But with COM it's usually a different story - the members should always just be there. Do the interop libraries use

Re: [IronPython] Revisiting interfaces and COM

2009-03-16 Thread Dino Viehland
Subject: [IronPython] Revisiting interfaces and COM From IronPython I'm calling ArcObjects, a large COM library that uses interfaces extensively. A .NET interoperability library is provided by the vendor. Currently I'm calling these interfaces as follows, but it's getting verbose very quickly

[IronPython] Revisiting interfaces and COM

2009-03-15 Thread Alex Willmer
From IronPython I'm calling ArcObjects, a large COM library that uses interfaces extensively. A .NET interoperability library is provided by the vendor. Currently I'm calling these interfaces as follows, but it's getting verbose very quickly: IFooBar.Foo(object, arg) # Foo is a method