views:

842

answers:

3

I'm fiddling with calling DLLs from C#, and came across the need to define my own structs. Lots of articles force a sequential layout for the struct with

[StructLayout(LayoutKind.Sequential)]
struct Foo ...

So, I followed suite, and my programme worked. Now, when I took the line out, it still works. Why do I need it?

+3  A: 

The internal layout of a managed struct is undocumented and undiscoverable. Implementation details like member order and packing are intentionally hidden. With the [StructLayout] attribute, you force the P/Invoke marshaller to impose a specific layout and packing.

That the default just happens to match what you need to get your code to work is merely an accident. Although not an uncommon one. Note the Type.StructLayoutAttribute property.

Hans Passant
Thanks for the answer. I just had a look at StructLayoutAttribute of my struct with and without that line. Seems both give me sequential. Is that the default?
biozinc
Yes. I have to type 10 chars for some reason...
Hans Passant
A: 

I am not entirely sure, but it may affect binary serialization - it might spit out the fields in order with not naming or ordering information (resulting in a smaller file), but that is a complete whim.

Jonathan C Dickinson
A: 

Interesting point. I'm sure I had code that failed until I put in an explicit LayoutKind.Sequential, however I have confirmed Sequential is the default for structures even in 1.1.

Note the VB Reference for Structure implies at Remarks > Behaviour > Memory Consumption that you do need to specify StructLayout to confirm the memory layout, but the documentation for StructLayoutAttribute states Sequential is the default for structures in Microsoft compilers.

Mark Hurd