Pinning Array

[Miguel]

When invoking the WaitForMultipleObjects function, should the second
parameter, which is een array, be pinned? I believe this should be the
case, since the CLR could move the array on the managed heap. However,
I have never experienced problems when not doing it.
Any ideas?

DWORD WaitForMultipleObjects(
DWORD nCount,
CONST HANDLE* lpHandles,
BOOL fWaitAll,
DWORD dwMilliseconds
);


In .NET I would use an array of integers or IntPtr.

 

[Guest]

The Marshaler will probably copy and pin it as long as the native call lasts.

 

[Miguel]

For avoiding any mistakes, I am referring to the .NET CF 1.0.

 

[Alex Feinman [MVP]]

I concur. For synchronous calls Marshaller pins variables for the duration
of the call