On Tue, 2004-06-01 at 19:42, Mike Hearn wrote:
> > Yes, you're right. I had initially thought that it was all done in
> > RPCRT4, but it looks like it is spread out across both libraries.
>
> There is an article somewhere that explains how it works. Basically the
> ITypeInfo (sorry not ITypeLib)
On Tue, 2004-06-01 at 19:26 +0100, Robert Shearman wrote:
> No, we actually do proper marshalling. This is either via the generated
> *_p.c files or via the type library marshaller. In the *_p.c case, the
> proxies are generated in dlls/rpcrt4/cproxy.c and the stubs in cstub.c
> The last bit of poi
On Tue, 2004-06-01 at 17:27, Mike Hearn wrote:
> On Tue, 2004-06-01 at 16:56 +0100, Robert Shearman wrote:
> > Even on Wine, those other functions, such as CoMarshalInterface do
> > actually attempt to get a marshaller or just use the standard one and
>
> and ... ?
>
> You mean it correctly doe
On Tue, 2004-06-01 at 16:56 +0100, Robert Shearman wrote:
> Actually, it does. It appears as though the interface marshaling
> functions are all compatible with each other on Windows (even though
> MSDN says that they aren't and then says they use the same code as the
> others). Presumably InstallS
On Sat, 2004-05-29 at 00:44, Mike Hearn wrote:
> Of course calling CoMarshalInterface in this case doesn't actually do
> much, but if it helps InstallShield OK.
Actually, it does. It appears as though the interface marshaling
functions are all compatible with each other on Windows (even though
MSD
( again wishing pan respected reply-to fields ... )
On Sat, 29 May 2004 00:33:24 +0100, Robert Shearman wrote:
> This patch fixes CoMarshalInterThreadInterfaceInStream and
> CoGetInterfaceAndReleaseStream to match what MSDN says - calling
> CoMarshalInterface and CoUnmarshalInterface respectively.
