4 ms·
Indeed, Victor Ciura from Microsoft DevDiv has several talks on how this is currently an adoption problem at Microsoft. They have been working around it with D
by pjmlp 9mo ago
Indeed, Victor Ciura from Microsoft DevDiv has several talks on how this is currently an adoption problem at Microsoft.
They have been working around it with DLLs, and COM/WinRT, but still the tooling isn't ideal.
- rhdunn 9mo agoCOM is interesting as it implements interfaces using the C++ vtable layout, which can be done in C. Dynamic COM (DCOM) is used to provide interoperability with Visual Basic. You can also access .NET/C# objects/interfaces via COM. It has an interface to allow you to get the type metadata but that isn't necessary. This makes it possible to e.g. get the C#/.NET exception stack trace from a C/C++ application.
- tonyedgecombe 9mo ago>Dynamic COM (DCOM) is used to provide interoperability with Visual Basic. DCOM is Distributed COM not Dynamic COM[1]. COM does have an interface for dynamic dispatch called IDispatch[2] which is used for scripting languages like VBScript or JScript. It isn't required for Visual Basic though. VB is compiled and supports early binding to interfaces. [1] https://en.wikipedia.org/wiki/Distributed_Component_Object_Model https://en.wikipedia.org/wiki/Distributed_Component_Object_M... [2] https://en.wikipedia.org/wiki/IDispatch https://en.wikipedia.org/wiki/IDispatch
- rhdunn 9mo agoAh yes, that's what I was thinking of. It's been a while since I've worked with COM.
- deleted 9mo ago[deleted]
- deleted 9mo ago[deleted]