tag:blogger.com,1999:blog-7907132636558724853.post4022750733439003654..comments2009-08-31T14:37:43.945-06:00Tyler Mercierhttps://profiles.google.com/118348864204478517743noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7907132636558724853.post-10345442228265483372009-08-31T10:14:33.103-06:002009-08-31T10:14:33.103-06:00Overall this is a comparison of value vs. reference types. <br /><br />As you mentioned, I think structs should only be used for small and immutable objects. Messages, depending on the implementation, should probably not be structs IMO.<br /><br />One thing that you didn&#39;t talk about was value type) in a method or a wrapping object boxing/unboxing. Whenever you use the struct (a (e.g. array) that takes a reference type (object-derrived) the struct will be copied to the heap anyways. Also, if one is using any reference types within the struct (e.g. string, arrays, etc.) they are already using the heap and simply performing a shallow copy when replicating the struct.Jason Morsehttp://blog.eveningcreek.comnoreply@blogger.com