Idiomatic bool marshalling about cswin32 HOT 4 CLOSED

BOOL appears in many places, including fields of structs, where marshaling is not always desirable or possible. However your doc snippet suggests that we can use bool (without marshaling) everywhere that BOOL appears, and that we should use a 1-byte representation wherever the native code uses bool.

@sotteson1, does the Win32 API ever use the native bool type (1-byte in length)? And if so, how is it represented in the metadata? It sounds like we can use System.Boolean for the 4-byte BOOL and should use something else for the C 1-byte bool type other than System.Boolean.

from cswin32.

I'm not sure why we would use the System.Boolean, as BOOL in Win32 is simply an 32-bit int. Using a NativeTypedef struct for the Win32 BOOL seems to be closer to the spirit of what the Win32 BOOL is.

from cswin32.

Thanks for chiming in, @sotteson1. I guess for proper interop on the CLR and better C# language experience, we can change all references from BOOL to bool in CsWin32.

from cswin32.

I just tried replacing all uses of BOOL with bool in our projection, but although the default interop size may be the same (4 bytes) between the two, evidently the CLR still considers bool to be a marshaled type, which makes it intolerable for use as a field in a struct, at least until #26 is delivered and only for customers using that setting.

from cswin32.